public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Theodore Tso <tytso@mit.edu>,
	Christoph Hellwig <hch@infradead.org>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 7/8] inode-diet: Use a union for i_blocks and i_size, i_rdev and i_devices
Date: Mon, 03 Jul 2006 08:18:59 -0700	[thread overview]
Message-ID: <44A93563.70601@zytor.com> (raw)
In-Reply-To: <20060703140217.GA8099@thunk.org>

Theodore Tso wrote:
> On Mon, Jul 03, 2006 at 10:06:42AM +0100, Christoph Hellwig wrote:
>> On Sun, Jul 02, 2006 at 08:53:40PM -0400, Theodore Ts'o wrote:
>>> The i_blocks and i_size fields are only used for regular files.  So we
>>> move them into the union, along with i_rdev and i_devices, which are
>>> only used by block or character devices.
>> Can we please make this a named instead of unnamed union so everyone still
>> using the fields will trip up?  To reduce the impact a few more imajor/iminor
>> conversions might be needed were direct references to i_rdev crept back in.
> 
> I did that originally but when I sent out my first version of patches
> for review, other developers asked me to use an unnamed union ---
> since otherwise the patch would be much, much larger (lots of changes
> would need to be made) and that makes it much harder to merge into
> either Andrew's or Linus's tree.
> 
> What do other people think?  I can go either way on this one.
> 

I think people need to know they're using a union, and hence it should 
be named.  Otherwise it's really easy to stare blindly at a piece of 
code, not understanding why touching i_foo affects i_bar.

	-hpa

  parent reply	other threads:[~2006-07-03 15:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  0:53 [patch 0/8] Inode slimming patches, part 1 Theodore Ts'o
2006-07-03  0:53 ` [patch 1/8] inode_diet: Replace inode.u.generic_ip with inode.i_private Theodore Ts'o
2006-07-03  0:53 ` [patch 2/8] inode-diet: Move i_pipe into a union Theodore Ts'o
2006-07-03  0:53 ` [patch 3/8] inode-diet: Move i_bdev " Theodore Ts'o
2006-07-03  0:53 ` [patch 4/8] inode-diet: Move i_cdev " Theodore Ts'o
2006-07-03  0:53 ` [patch 5/8] inode-diet: Eliminate i_blksize and use a per-superblock default Theodore Ts'o
2006-07-03  0:53 ` [patch 6/8] inode-diet: Move i_cindex from struct inode to struct file Theodore Ts'o
2006-07-03  9:05   ` Christoph Hellwig
2006-07-03 14:05     ` Theodore Tso
2006-07-03  0:53 ` [patch 7/8] inode-diet: Use a union for i_blocks and i_size, i_rdev and i_devices Theodore Ts'o
2006-07-03  8:27   ` Andrew Morton
2006-07-03 14:35     ` Hugh Dickins
2006-07-03  9:06   ` Christoph Hellwig
2006-07-03 14:02     ` Theodore Tso
2006-07-03 14:42       ` Jan Engelhardt
2006-07-03 15:18       ` H. Peter Anvin [this message]
2006-07-03  0:53 ` [patch 8/8] inode-diet: Fix size of i_blkbits, i_version, and i_dnotify_mask Theodore Ts'o

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=44A93563.70601@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --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