On Tue, May 22, 2007 at 08:44:30PM +1000, David Chinner wrote:
quoted text
> Perhaps a new field in the xfs_buf structure - that way call paths
> don't need to grow extra parameters and potentially increase
> stack usage. The read path tends to be at the top of the stack
> when it gets blown in the writeback path....

I have some patches to unwind the buffer I/O path, it's a little
to overcomplicated due to historical reasons.

quoted text
> >    the offset in xlog_sync aswell.
> 
> I don't want to have to introduce a mempool just for one xfs_buf per
> filesystem, so this would need to be able to take a xfs_buf (log->l_xbuf)
> that it clones to....

Yes.  Note that we currently do a non-mempooled allocated for the page
array, which this would cure aswell.
-
unsubscribe notice
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/