pthreads and kqueue

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,

Re: pthreads and kqueue

"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 thr

Re: Kevents/libc_r ?

"Jeff Roberson" <[EMAIL PROTECTED]> writes: > Is that true in -CURRENT as well? It looks to me like it calls kevents with > a 0 timespec and then calls into the scheduler. > > > * Jeff Roberson <[EMAIL PROTECTED]> [010130 11:05] wrote: > > > Does anyone know if it's safe to use kevents with pth

kqueue/kevent and OOB?

Greetings! How does kevent signal out-of-band data? When using select, I can check the fd set for an exception. How do I know when out-of-band has arrived when using kevent? Thanks for any help, km To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body

aio_waitcomplete?

In order to get familiar with aio_waitcomplete() and friends, I wrote a simple echo server and have run into problems. If I attempt to hit my echo server with more than a few clients (> 3 or 4), I get a bunch of ENOTCONN errors from aio_waitcomplete() and on the client end I get an ECONNRESET an

RE: freebsd and non-preemtive threads

> > This reminds me of coroutines or userland select- or kqueue-based > "threading." Coroutines is a bit more complex but a library is > available. I've seen the term 'kqueue-based threading' on this list a few times now. Could you explain what you mean by that? Thanks! To Unsubscribe: send

atomic operations

I found the atomic_* functions in , but noticed that they have no return value. What I need is a function that increments/decrements the given value *and* returns the new value in an atomic operation. I suppose this is possible, yes? How would one modify the assembly to make this work? Thanks