Tell me what I misunderstood. As far as I can tell, pre patch behavior
involves many fewer calls to schedule, post patch behavior for a write, for
example, can make at least one extra call to the scheduler for every block
copied. If "needs_resched >0" it is still not necessarily true that the
call to the scheduler is "necessary". Consider, a long running data base
program is writing backing store out to disk. Old behavior: the write
absorbs as much free memory as possible to optimize disk behavior. New
behavior: a screen saver, which is small i/o bound, causes needs resched
to be set continually, and the write is segmented into many smaller writes.
We now have, like NT, optimized the screen saver on a server while hammering
file system performance. Isn't that correct?
-
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/