Date: Sun, 9 Nov 2014 23:16:37 -0800 From: Jordan Hubbard <jkh@mail.turbofuzz.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: freebsd-hackers@freebsd.org, J David <j.david.lists@gmail.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: How thread-friendly is kevent? Message-ID: <500974D4-581E-46CB-9DC8-A100AAD35F70@mail.turbofuzz.com> In-Reply-To: <20141110071353.GO24601@funkthat.com> References: <CABXB=RQWxu-d30raZ%2BFcrnrGsr5gG2Za_=cx8-jCnLSgJDSF=Q@mail.gmail.com> <20141110071353.GO24601@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 9, 2014, at 11:13 PM, John-Mark Gurney <jmg@funkthat.com> = wrote: >=20 > The most common use of this is for socket IO (there isn't much else > except maybe vnodes) that you can wait on that you'd have such a = highly > multithreaded program... And if you do, it would make more sense to > use the recent RSS work that Adrian has been working on, and have one > kq per CPU w/ the proper cpu binding for that set of sockets... Or just use libdispatch, which feeds a pool of worker threads from a = single event-handling source that is kind to queues. :) - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?500974D4-581E-46CB-9DC8-A100AAD35F70>