Re: 210ms interval between two schedule() calls - is it possible?

From: Artur Skawina (skawina@geocities.com)
Date: Fri Feb 18 2000 - 02:09:44 EST


Jun Sun wrote:
>
> I did a very simple timing experiement: measure the interval between
> two consequtive calls to schedule() function.
>
> Under light load situation, the maximum interval is around 10ms which is
> the time slicing interval. However, if I increase the load (actually I
> was running NIST POSIX test suite), the maximum interval could go
> up to 210ms.
>
> Is this possbile? Should the kernel at very least obey the time
> slicing,
> which I expect schedule() should be called no more than every 10ms.

the scheduler only gets called when potentially there's something
else to schedule, the current thread uses up its quantum (~200ms) or blocks.

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



This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:21 EST