From: Nathan Scott <nathans@sgi.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Slimming down struct inode
Date: Tue, 13 Jun 2006 14:32:31 +1000 [thread overview]
Message-ID: <20060613143230.A867599@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0606101237020.23706@yvahk01.tjqt.qr>; from jengelh@linux01.gwdg.de on Sat, Jun 10, 2006 at 12:48:27PM +0200
On Sat, Jun 10, 2006 at 12:48:27PM +0200, Jan Engelhardt wrote:
>
> >1) Move i_blksize (optimal size for I/O, reported by the stat system
> > call). Is there any reason why this needs to be per-inode, instead
> > of per-filesystem?
Sorry, missed this on the first reading - yes, there are reasons
for doing this per inode, as Jan points out...
> I do not know much about XFS's realtime feature, but from what I have read
> about it so far, it sounds to be a potential source where i_blksize might
> differ from the regular filesystem. A guess, though.
Such a change would would indeed break XFS, in exactly the way you
suggest Jan - the realtime subvolume does typically use a different
blocksize from the data subvolume (the realtime extent size is used,
and this can be set per-inode too), and there would now be no way to
distinguish this preferred IO size difference.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-06-13 4:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 23:50 Theodore Ts'o
2006-06-10 0:24 ` Bernd Eckenfels
2006-06-10 1:27 ` Al Viro
2006-06-10 1:56 ` Theodore Tso
2006-06-10 6:24 ` Stefan Richter
2006-06-10 10:48 ` Jan Engelhardt
2006-06-10 15:04 ` Jeff Garzik
2006-06-13 4:35 ` Nathan Scott
2006-06-13 4:32 ` Nathan Scott [this message]
2006-06-13 14:00 ` Avi Kivity
2006-06-13 17:44 ` Theodore Tso
2006-06-13 18:08 ` Avi Kivity
2006-06-13 20:10 ` Jan Engelhardt
2006-06-13 20:25 ` Avi Kivity
2006-06-13 22:41 ` Nathan Scott
2006-06-14 10:29 ` Nikita Danilov
2006-06-14 21:50 ` Nathan Scott
2006-06-15 5:49 ` Theodore Tso
2006-06-15 7:01 ` Nathan Scott
2006-06-15 8:46 ` Brian F. G. Bidulock
2006-06-15 10:20 ` Nathan Scott
2006-06-14 23:27 ` Jan Engelhardt
2006-06-15 10:09 ` Nikita Danilov
2006-06-10 11:03 ` Tomasz Torcz
2006-06-10 15:06 ` Jeff Garzik
2006-06-15 0:16 ` Brian F. G. Bidulock
2006-06-15 4:43 ` Theodore Tso
2006-06-15 8:27 ` Brian F. G. Bidulock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060613143230.A867599@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®