Re: [2.4.17/18pre] VM and swap - it's really unusable

Allan Sandfeld
2002-01-21T20:19:40Z

On Monday 21 January 2002 20:26, Mark Hahn wrote:
> > > > To me the benefit is clear enough: ASAP scheduling of IO threads, a
> > > > simple heuristic that improves both throughput and latency.
> > >
> > > I think of "benefit", perhaps naiively, in terms of something that can
> > > be measured or demonstrated rather than just announced.
> >
> > But you see why asap scheduling improves latency/throughput *in theory*,
> > don't you?
>
> NO, IT DOES NOT. why can't you preempt-ophiles get that through your heads?
>
> eager scheduling is NOT optimal in general.
>
> for instance, suppose my disk can only read a sector at a time.
> scheduling my sequentially-reading process to wake eagerly
> is most definitly PESSIMAL. laziness is a cardinal virtue!
> this doesn't preclude heuristics to sometimes short-cut the laziness.
>
It's because your system is behaving wrongly for your dream to come true. If
your want to handle several expected inputs from IO, you should ask it for an
interrupt for every package. Rather you should rely on a timer function an
periodically handle new data and in case of nothing new, go back to
interrupts..

Eager scheduling is OPTIMAL for the sematics in your system. It thats is not
optimal for throughput/whatever, it's the code that is wrong!

-Allan