Re: [RFC] generic IO write clustering

2001-01-20 Thread Marcelo Tosatti
On Sat, 20 Jan 2001, Christoph Hellwig wrote: > On Sat, Jan 20, 2001 at 02:00:24PM -0200, Marcelo Tosatti wrote: > > > True. But you have to go through ext2_get_branch (under the big kernel > > > lock) - if we can do only one logical->physical block translations, > > > why doing it multiple tim

Re: [RFC] generic IO write clustering

2001-01-20 Thread Christoph Hellwig
On Sat, Jan 20, 2001 at 02:00:24PM -0200, Marcelo Tosatti wrote: > > True. But you have to go through ext2_get_branch (under the big kernel > > lock) - if we can do only one logical->physical block translations, > > why doing it multiple times? > > You dont. If the metadata is cached and uptodat

Re: [RFC] generic IO write clustering

2001-01-20 Thread Marcelo Tosatti
On Sat, 20 Jan 2001, Christoph Hellwig wrote: > On Sat, Jan 20, 2001 at 01:24:40PM -0200, Marcelo Tosatti wrote: > > In case the metadata was not already cached before ->cluster() (in this > > case there is no disk IO at all), ->cluster() will cache it avoiding > > further disk accesses by writ

Re: [RFC] generic IO write clustering

2001-01-20 Thread Christoph Hellwig
On Sat, Jan 20, 2001 at 01:24:40PM -0200, Marcelo Tosatti wrote: > In case the metadata was not already cached before ->cluster() (in this > case there is no disk IO at all), ->cluster() will cache it avoiding > further disk accesses by writepage (or writepages()). True. But you have to go throu

Re: [RFC] generic IO write clustering

2001-01-20 Thread Marcelo Tosatti
On Sat, 20 Jan 2001, Christoph Hellwig wrote: > I think there is a big disadvantage of this appropeach: > To find out which pages are clusterable, we need do do bmap/get_block, > that means we have to go through the block-allocation functions, which > is rather expensive, and then we have to d

Re: [RFC] generic IO write clustering

2001-01-20 Thread Christoph Hellwig
In article <[EMAIL PROTECTED]> you wrote: > The write clustering issue has already been discussed (mainly at Miami) > and the agreement, AFAIK, was to implement the write clustering at the > per-address-space writepage() operation. > IMO there are some problems if we implement the write clusterin

Re: [RFC] generic IO write clustering

2001-01-19 Thread Marcelo Tosatti
On Sat, 20 Jan 2001, Rik van Riel wrote: > Is there ever a reason NOT to do the best possible IO > clustering at write time ? > > Remember that disk writes do not cost memory and have > no influence on the resident set ... completely unlike > read clustering, which does need to be limited. You

Re: [RFC] generic IO write clustering

2001-01-19 Thread Rik van Riel
On Fri, 19 Jan 2001, Marcelo Tosatti wrote: > The write clustering issue has already been discussed (mainly at Miami) > and the agreement, AFAIK, was to implement the write clustering at the > per-address-space writepage() operation. > > IMO there are some problems if we implement the write clust

[RFC] generic IO write clustering

2001-01-19 Thread Marcelo Tosatti
Hi, I'm starting to implement a generic write clustering scheme and I would like to receive comments and suggestions. The write clustering issue has already been discussed (mainly at Miami) and the agreement, AFAIK, was to implement the write clustering at the per-address-space writepage() ope