mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Theodore Tso <tytso@mit.edu>,
	Nikita Danilov <nikita@clusterfs.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC]  Slimming down struct inode
Date: Thu, 15 Jun 2006 17:01:36 +1000	[thread overview]
Message-ID: <20060615170136.D898607@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060615054931.GC7318@thunk.org>; from tytso@mit.edu on Thu, Jun 15, 2006 at 01:49:31AM -0400

Hi Ted,

On Thu, Jun 15, 2006 at 01:49:31AM -0400, Theodore Tso wrote:
> On Thu, Jun 15, 2006 at 07:50:19AM +1000, Nathan Scott wrote:
> > As to whether a new inode operation is useful/needed - *shrug* - not
> > really my call, I was saying we can work with whatever ends up being
> > the final solution, provided it keeps per-inode granularity.
> 
> XFS should be return a per-inode value for st_blksize by simply setting
> kstat->st_blksize in linvfs_getattr() found in fs/xfs/linux-2.6/xfs_iops.c.

Hmm, you're looking at an older kernel there I guess - that routine
doesn't exist anymore.  Look at -mm, its the most recent version.

> in the Irix/Linux compatibility layer (yuck, I still can't believe
> this got into mainline),

There is no IRIX/Linux compatibility layer, you're misunderstanding
the code (which is understandable, its erm a bit crufty in places).
There's a fair bit of history there too - *shrug* - its on the improve
but its a complex body of code and takes time to mutate.  We've tended
to focus on real problems and needed features in the past, moreso than
cosmetics, but thats getting attention nowadays too.

> I'll let the XFS maintainers decide how put in per-inode st_blksize
> values --- but it is definitely doable.

Yep, agreed.

cheers.

-- 
Nathan

  reply	other threads:[~2006-06-15  7:02 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
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 [this message]
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=20060615170136.D898607@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita@clusterfs.com \
    --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®