.
I know manpages are a poor source for references but you're the one
putting up a big fight for blocking behavior from poll, perhaps you
can point out a standard that contradicts the manpages?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I
an application won't care about I don't
think that would be taken back.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
n EBADF when it goes
to perform the read.
Another thread may already have reused the fd
This is another example of an application threading problem.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
-
To unsubscribe
* Jamie Lokier [EMAIL PROTECTED] [001027 08:21] wrote:
Alfred Perlstein wrote:
If a programmer does not ever wish to block under any circumstances, it's
his obligation to communicate this desire to the implementation. Otherwise,
the implementation can block if it doesn't have data
ng kevent() noticing.)
Yes, that's how it does and should work. Noticing the close()
should be done via thread communication/IPC not stuck into
kqueue.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
-
To un
r would be acceptable, but surely not blocking.
I know manpages are a poor source for references but you're the one
putting up a big fight for blocking behavior from poll, perhaps you
can point out a standard that contradicts the manpages?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]
if you
make kqueue generate info an application won't care about I don't
think that would be taken back.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."
-
To unsubscribe from this list: send the line "un
one thread closes
> > the descriptor, the other thread is going to get an EBADF when it goes
> > to perform the read.
>
> Another thread may already have reused the fd
This is another example of an application threading problem.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMA
* Jamie Lokier <[EMAIL PROTECTED]> [001027 08:21] wrote:
> Alfred Perlstein wrote:
> > > If a programmer does not ever wish to block under any circumstances, it's
> > > his obligation to communicate this desire to the implementation. Otherwise,
> > > the im
fd 5.
>
> (I suspect it helps that kevent() is both the only way to
> bind events and the only way to pick them up; makes it harder
> for one thread to sneak a new fd into the event list without
> the thread calling kevent() noticing.)
Yes, that's how it does and should work. Noticing the clos
10 matches
Mail list logo
