public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC]  Slimming down struct inode
Date: Thu, 15 Jun 2006 00:43:02 -0400	[thread overview]
Message-ID: <20060615044302.GA7318@thunk.org> (raw)
In-Reply-To: <20060614181627.B28144@openss7.org>

On Wed, Jun 14, 2006 at 06:16:27PM -0600, Brian F. G. Bidulock wrote:
> > 3) Move i_pipe, i_bdev, and i_cdev into a union.  An inode cannot
> >     simultaneously be a pipe, block device, and character device at the
> >     same time.
> 
> A STREAMS-based FIFO is both a (named) pipe and a character device at the
> same time.  I would prefer if you did not merge i_pipe with i_cdev for this
> reason.  In the current GPL'ed out of tree STREAMS implementation, i_pipe
> is used to point to the Stream head (as the normal v_str pointer in the UNIX
> vnode).  

I'm not particularly sympathetic to out of tree implementations,
especially one which is as (NOT!) likely to be merged as STREAMS
support.  Out of tree patches can always patch struct inode to add all
the bloat they want.  Also, it souinds like you're not usually using
i_pipe as a true pointer to a struct pipe_inode_info, but rather as
kludged location to stash your v_str pointer.  Why not just have your
STREAMS implementation patch include/linux/fs.h to add a v_str pointer?

						- Ted

  reply	other threads:[~2006-06-15  6:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 23:50 [RFC] Slimming down struct inode 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
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 [this message]
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=20060615044302.GA7318@thunk.org \
    --to=tytso@mit.edu \
    --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