From: Nathan Scott <nathans@sgi.com>
To: Avi Kivity <avi@argo.co.il>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Slimming down struct inode
Date: Wed, 14 Jun 2006 08:41:55 +1000 [thread overview]
Message-ID: <20060614084155.C888012@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <448EC51B.6040404@argo.co.il>; from avi@argo.co.il on Tue, Jun 13, 2006 at 05:00:59PM +0300
On Tue, Jun 13, 2006 at 05:00:59PM +0300, Avi Kivity wrote:
> Nathan Scott wrote:
> > Such a change would would indeed break XFS, in exactly the way you
Oh, I should clarify - the suggestion of using sb->s_blocksize/
s_blocksize_bits was what I meant by "would break XFS".
> > 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.
>
> It can be made into an inode operation:
*nod* - that'd work fine for our needs here.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-06-13 22:42 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
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 [this message]
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=20060614084155.C888012@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=avi@argo.co.il \
--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®