All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Dave Jones <davej@codemonkey.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: struct inode size reduction.
Date: Sun, 9 Mar 2003 18:13:14 +0100	[thread overview]
Message-ID: <20030309171314.GA3783@win.tue.nl> (raw)
In-Reply-To: <20030309135402.GB32107@suse.de>

On Sun, Mar 09, 2003 at 12:54:03PM -0100, Dave Jones wrote:
> Third retry, perhaps it'll make it through to the list
> now that vger is sending mail again...

> I've been running with this patch, with no untoward consequences,
> seems to pass basic testing here, any objections before I push
> this Linuswards ? Al ? Christoph ?
> 
> --- bk-linus/include/linux/fs.h	2003-03-08 08:57:57.000000000 -0100
> +++ inode/include/linux/fs.h	2003-03-08 08:57:20.000000000 -0100
> @@ -382,12 +382,12 @@ struct inode {
>  	struct address_space	*i_mapping;
>  	struct address_space	i_data;
>  	struct dquot		*i_dquot[MAXQUOTAS];
> -	/* These three should probably be a union */
>  	struct list_head	i_devices;
> -	struct pipe_inode_info	*i_pipe;
> -	struct block_device	*i_bdev;
> -	struct char_device	*i_cdev;
> -
> +	union {
> +		struct pipe_inode_info	*i_pipe;
> +		struct block_device	*i_bdev;
> +		struct char_device	*i_cdev;
> +	} type;

Not really any objection, but this is half work where
more can be done. The comment is right: also i_devices
can go into the union.
(And i_cdev can be deleted altogether, but that is an
independent matter.)

Andries



  reply	other threads:[~2003-03-09 17:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 13:54 Fwd: struct inode size reduction Dave Jones
2003-03-09 17:13 ` Andries Brouwer [this message]
2003-03-09 20:33   ` Dave Jones
2003-03-09 19:55     ` Christoph Hellwig
2003-03-09 20:31       ` Andries Brouwer
2003-03-09 22:18         ` Roman Zippel
2003-03-09 23:08           ` Andries Brouwer
2003-03-10  2:23             ` Alexander Viro
2003-03-10 10:58             ` Roman Zippel
2003-03-10 12:05               ` Andries Brouwer
2003-03-10 16:25                 ` Roman Zippel
2003-03-10 17:32                   ` Andries Brouwer
2003-03-10 18:39                     ` Roman Zippel
2003-03-09 22:45 ` J.A. Magallon
2003-03-10  0:11   ` Dave Jones
2003-03-09 23:59     ` J.A. Magallon
2003-03-10  5:04       ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10  9:30 Fwd: " Andries.Brouwer
2003-03-10  9:32 Andries.Brouwer

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=20030309171314.GA3783@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.