Messages in this thread | | | Date | Wed, 3 Dec 2014 13:11:28 +1100 | Subject | Re: [PATCH 1/2] fs: introduce sendfd() syscall | From | Alex Dubov <> |
| |
On Wed, Dec 3, 2014 at 3:42 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote: > On Wed, 2014-12-03 at 03:23 +1100, Alex Dubov wrote: > > Tell me how a 128 threads program can use this new mechanism in a > scalable way. > > One signal per thread ?
What for?
Kernel will deliver the signal only to the thread/threads which has the relevant signal unblocked (they are blocked by default).
> > I guess we'll keep AF_UNIX then, thank you.
Kindly enlighten me, how are you going to use any file descriptor in a 128 threads program in a scalable way (socket and all)? How this approach will be different when using signalfd()?
And no, I'm not proposing to take your favorite toys away.
| |