Re: [patch 14/22] pollfs: pollable futex

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/2/07, Davide Libenzi <[email protected]> wrote:
99% of the fds you'll find inside an event loop you care to scale about,
are *already* fd based.

You are missing the point.  To get acceptable behavior of the wakeup
it is necessary with this approach to open one descriptor _per thread_
for a futex.  Otherwise all threads get woken upon FUTEX_WAKE.

This also means you need individual epoll sets for each thread.  You
cannot share them anymore among all the threads in the process.


On top of that, those fds are very cheap in terms of memory

They might be when they are counted in dozens.  But here we are
talking about the possible need to use thousands of additional file
descriptors.  If they are so cheap to allow thousands of descriptors
with ease, why would the rlimit for files default to a small number
(1024 on Fedora right now)?


And this approach is not bound to a completely new and monolitic interface.

So?  It's stil additional, new code for an approach which will have to
be superceded real soon.  That's just pure overhead to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux