[Top] [All Lists]

Re: TAKE - pagebuf

To: Eric Sandeen <sandeen@xxxxxxx>
Subject: Re: TAKE - pagebuf
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 9 May 2002 08:56:07 +1000
Cc: Austin Gonyou <austin@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1020874330.30053.2.camel@xxxxxxxxxxxxxxxxxxxxxx>; from sandeen@xxxxxxx on Wed, May 08, 2002 at 11:12:09AM -0500
References: <200205080421.OAA52473@xxxxxxxxxxxxxxxxxxxxxxx> <1020871711.19190.18.camel@UberGeek> <1020874330.30053.2.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Wed, May 08, 2002 at 11:12:09AM -0500, Eric Sandeen wrote:
> On Wed, 2002-05-08 at 10:28, Austin Gonyou wrote:
> > Curious to know what is being considered *small block*? (2k 1k?)
> Anything less than page size.
> And "boost performance" does not mean that reducing your block size is a
> performance enhancer; the mod you mentioned was more along the lines of
> "less slow," not "super fast."

This mod gets <pgsize blks up to about the same as pgsize for specific
workloads/machine configs (it is a huge boost over the previous code).
So, it's better than less slow, but not quite super fast yet. ;)  But,
its all academic at this stage, since...

> Note that none of this stuff is ready for prime-time yet, either... You
> should assume that the block size == page size restriction is still in
> place, for now.

It _is_ still in place (the Linux/XFS mount code path doesn't allow fs's
with non-pgsize blocks), no assumption about it.  There is still plenty
to be done before we drop this check I think, but not too far off now.



<Prev in Thread] Current Thread [Next in Thread>