Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available

From: Martin MaD Douda (martin@douda.net)
Date: Sat Jan 20 2001 - 07:26:08 EST

Next message: Matthias Schniedermeyer: "Re: Mainboard with Serverworks HE Chipset"
Previous message: Nick Urbanik: "Re: rsync + ssh fail on raid; okay on 2.2.x"
In reply to: Michael Lindner: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Next in thread: Bjorn Wesen: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Reply: Bjorn Wesen: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Matthias Schniedermeyer: "Re: Mainboard with Serverworks HE Chipset"
Previous message: Nick Urbanik: "Re: rsync + ssh fail on raid; okay on 2.2.x"
In reply to: Michael Lindner: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Next in thread: Bjorn Wesen: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Reply: Bjorn Wesen: "Re: PROBLEM: select() on TCP socket sleeps for 1 tick even if data available"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jan 23 2001 - 21:00:22 EST