On 25 Jan 2001, Kevin Mills wrote:
> Well, there are wrappers in the libc_r code (libc_r/uthread/uthread_kevent.c)
> and I seem to recall posts on -stable saying that kqueue could now be used
> with user threads (around the 4.1.1 time frame, I think).
I could be wrong :)
> > This seems like a
"Doug White" <[EMAIL PROTECTED]> writes:
> On 24 Jan 2001, Kevin Mills wrote:
>
> You should probably assume that kqueue/kevent() & friends are not
> thread-safe. I would suggest using a separate dispatcher thread that sits
> on the kqueue and wakes up threads as needed. This would be much mor
On 24 Jan 2001, Kevin Mills wrote:
> My question: Is it considered "safe" to have a number of threads each
> waiting on a call to kevent() using the same kqueue? Or do I need to
> have one thread waiting on the kevent() call and have it dispatch jobs
> to the waiting threads?
You should pro
A little background:
I have an application that uses kqueue to manage many, many sockets (and it
works wonderfully, btw). I'm using non-blocking I/O, so my application
can certainly work without threads. However, each incoming connection needs
to access a back-end RADIUS or LDAP server and,
4 matches
Mail list logo
