> On Sep 20, 2001 23:20 +0800, Beau Kuiper wrote:
> > Patch 3 doesn't improve performace much (even in theory the number of
> > dirty buffers being wrongly flushed is pretty low)
>
> Actually, it _may_ even make performance worse (hard to say). Consider
> the case where the "young" dirty buffers are in the same area of the
> disk as the "old" dirty buffers. Once you are forced to write the "old"
> buffers, you pretty much get to write the new buffers for free (low seek
> overhead). They _could_ be merged in the elevator code.
>
> Sadly, it is hard to tell whether this is possible or not, because the
> code to do these things live in different places. Maybe we could have
> an "optimistic" elevator merge, which only added "young" buffers if
> they merged with other old buffers.
But don't forget that when dirty buffers are being flushed, they become
locked while the disk update is occuring. That means any programs that are
still using these "young" dirty buffers must wait for disk io to complete
(including all the older buffers that have to be written to disk before
it). When several hundred other buffers are slso being flushed to disk by
kupdated , it could be a long wait.
Also, it is nicer behaviour not to write out to disk before the time
indicated in the bdflush tuning structure. It allows sys admins to better
tune the overal performace of a system. (unless the kernel need s more
free memory)
Have fun
Beau Kuiper
kuib-kl@ljbc.wa.edu.au
>
> Cheers, Andreas
> --
> Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
> \ would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/