Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1403705
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch V2 3/7] futex: Add op for hash preallocation |
| Date | 2016-05-19 14:30 +0200 |
| Message-ID | <rAvfr-8bz-1@gated-at.bofh.it> (permalink) |
| References | <rvynE-79b-3@gated-at.bofh.it> <rvynE-79b-1@gated-at.bofh.it> <rvSw1-1EJ-3@gated-at.bofh.it> <rw65Y-6Am-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, May 07, 2016 at 10:47:38AM +0200, Thomas Gleixner wrote: > On Fri, 6 May 2016, Darren Hart wrote: > > So this seems like it could be tricky for the user as system libraries, like > > glibc, make use of futexes. Can we guarantee that "sys_futex" is not called by > > the time main() is called? > > To the extent of my testing I never observed that the hash was automatically > created when I called futex(PREALLOC) right away in main. But yes, that might > need some thought. I suspect that even if glibc uses futexes before main(), they will not be contended, because, last time I checked, the C runtime environment is very much single threaded unless explicitly made not so by the program. In any case (re)hashing if the hash is empty is 'easy', if there's already state, not so much.
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [patch V2 3/7] futex: Add op for hash preallocation Peter Zijlstra <peterz@infradead.org> - 2016-05-19 14:30 +0200 Re: [patch V2 3/7] futex: Add op for hash preallocation Darren Hart <dvhart@infradead.org> - 2016-05-19 21:40 +0200
csiph-web