On 24 Jan 2001, David Wragg wrote:

> There's a patch for ext2 below for a quick and dirty implementation of
> block bitmap readahead.  But since I'm looking for comments, feedback,
> etc., rather than asking for the patch to be added to ext2 in the near
> future, I'll start at the beginning:>

<snip>

> It still needs some work.  With my data aquisition application, it
> will often do multiple readaheads for the same block bitmap.  I can
> probably get rid of those by tuning the heuristic, but I want to
> understand more about what causes them first.
> 
> Is this something worth including in ext2?  It only makes a difference
> to a very specific workload, but for that workload it gives a
> significant improvement, and it doesn't involve much extra code.

Additional caching of block locations makes read/write (once we have it)
clustering more efficient because it avoids additional accesses to disk
(which are going to cause seek time in the worst case).

Another thing you can try is to make the buffer cache shrinking (called
when memory shortage happens) less aggressive. (search for
kmem_cache_reap() on mm/)

> One possibility is that ext2 is the simply the wrong filesystem for my
> application, and any other applications that needs guaranteed
> sustained write bandwidth.  The obvious alternative is XFS.  However,
> early releases of Linux XFS will not feature the guaranteed rate I/O
> features, so that's not likely to be an option for quite a while yet.

Even without guaranteed rate IO XFS extents will probably make the
throughtput higher.
 


-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]

Reply via email to