On Fri, 19 Jan 2001, Michael Lindner wrote:
> data is generated as a result of data received via a select(),
> the next delivery occurs a clock tick later, with the machine
> mostly idle.
^^^^^^^^^^^
The machine is in fact not idle - there is a task running - idle task.
Could the problem be that scheduler does not preempt this task to run
something more useful?
Symptoms seems to show this.
Martin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
- PROBLEM: select() on TCP socket sleeps for 1 tick even if... Michael Lindner
- RE: PROBLEM: select() on TCP socket sleeps for 1 tic... David Schwartz
- Re: PROBLEM: select() on TCP socket sleeps for 1... Michael Lindner
- RE: PROBLEM: select() on TCP socket sleeps f... David Schwartz
- Re: PROBLEM: select() on TCP socket slee... Michael Lindner
- Re: PROBLEM: select() on TCP socket sleeps f... Martin MaD Douda
- Re: PROBLEM: select() on TCP socket slee... Bjorn Wesen
- Re: PROBLEM: select() on TCP socket sleeps for 1 tic... Boris Dragovic
- Re: PROBLEM: select() on TCP socket sleeps for 1 tic... Bernd Eckenfels
