lkml.org 
[lkml]   [2004]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: poll() in 2.6 and beyond


On Wed, 3 Mar 2004, Richard B. Johnson wrote:
>
> And YES! If I clear the flag only after it is read. It "fixes" the
> observed problem!

Ok. That solves one problem, but it does seem to point to the fact that
2.6.x calls down to poll() more than 2.4.x does.

It really _is_ normal to have multiple calls to "poll()" for the same fd
as a result of a single "poll()" system call, but if we actually get a
positive hit (ie the ->poll() call returns a bit that we consider to be a
success by comparing it to what we _wanted_ to see), then we should have
stopped doing that.

And since your test program always sets "POLLIN", any ->poll() call that
has the POLLIN flag set should have ended up being the last one (since it
would have marked a "success").

So there's still something I don't understand, and that seems to differ
between 2.4.x and 2.6.x. Can anybody else see it?

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [W:0.027 / U:2.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site