Date: Tue, 5 Aug 2003 12:09:46 -0600
From: Andreas Dilger <adilger@clusterfs.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: i_blksize
Message-ID: <20030805120946.Y4479@schatzie.adilger.int>
Mail-Followup-To: Andrew Morton <akpm@osdl.org>, Andries.Brouwer@cwi.nl,
	linux-kernel@vger.kernel.org, torvalds@osdl.org
References: <UTC200308051627.h75GR7J08241.aeb@smtp.cwi.nl> <20030805105006.2769e44a.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030805105006.2769e44a.akpm@osdl.org>; from akpm@osdl.org on Tue, Aug 05, 2003 at 10:50:06AM -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1108
Lines: 29

On Aug 05, 2003  10:50 -0700, Andrew Morton wrote:
> Andries.Brouwer@cwi.nl wrote:
> > Yes. But nevertheless, now that you brought this up,
> > we might consider throwing out i_blksize.
> > 
> > I am not aware of anybody who actually uses this to give
> > per-file advice. So, it could be in the superblock.
> 
> I suppose so.  reiserfs plays with it.
> 
> I can't really see that anyone would want to set the I/O size hint on a
> per-inode basis, especially as the readahead and writebehind code will
> cheerfully ignore it.

Actually, Lustre uses this, because each file can be striped over a
different number of storage targets, and you want read and write requests
large enough to try and write to all of the targets at one time.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

-
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/