Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1423264
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH-tip v2 5/6] locking/rwsem: Change RWSEM_WAITING_BIAS for better disambiguation |
| Date | 2016-06-15 19:50 +0200 |
| Message-ID | <rKn6V-5AD-7@gated-at.bofh.it> (permalink) |
| References | <rK5jH-2zl-5@gated-at.bofh.it> <rK5jH-2zl-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jun 14, 2016 at 06:48:08PM -0400, Waiman Long wrote: > even the reduced maximum of about 16k (32-bit) or 1G (64-bit) should > be more than enough for the foreseeable future. So what happens if I manage to create 16k+ threads on my 32bit kernel and get them all to do mmap() or so at the same time. That doesn't seem too far fetched. Then again, with double that (the current limit) that doesn't seem impossible either.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH-tip v2 5/6] locking/rwsem: Change RWSEM_WAITING_BIAS for better disambiguation Waiman Long <Waiman.Long@hpe.com> - 2016-06-15 00:50 +0200
Re: [RFC PATCH-tip v2 5/6] locking/rwsem: Change RWSEM_WAITING_BIAS for better disambiguation Peter Zijlstra <peterz@infradead.org> - 2016-06-15 19:50 +0200
Re: [RFC PATCH-tip v2 5/6] locking/rwsem: Change RWSEM_WAITING_BIAS for better disambiguation Peter Zijlstra <peterz@infradead.org> - 2016-06-15 19:50 +0200
Re: [RFC PATCH-tip v2 5/6] locking/rwsem: Change RWSEM_WAITING_BIAS for better disambiguation Peter Zijlstra <peterz@infradead.org> - 2016-06-16 00:00 +0200
csiph-web