public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: struct inode size reduction.
Date: Sun, 9 Mar 2003 19:33:59 -0100	[thread overview]
Message-ID: <20030309203359.GA7276@suse.de> (raw)
In-Reply-To: <20030309171314.GA3783@win.tue.nl>

On Sun, Mar 09, 2003 at 06:13:14PM +0100, Andries Brouwer wrote:

 > > -	/* 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.

The different size types threw me, and I figured it
was a misplaced comment. It certainly made more sense
that way when it mentioned 'these three' rather than
'these four'.  looking at bd_acquire I'm not so sure
it's as simple a job as the other three were.

 > (And i_cdev can be deleted altogether, but that is an
 > independent matter.)

There still seems to be some users of that, so I'll
leave that to a follow up patch, (or someone else who
really knows whats going on there).

		Dave


  reply	other threads:[~2003-03-09 19:25 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
2003-03-09 20:33   ` Dave Jones [this message]
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=20030309203359.GA7276@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=aebr@win.tue.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox