From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Alexander Viro <viro@math.psu.edu>,
Christoph Rohland <cr@sap.com>,
"David L. Parsley" <parsley@linuxjedi.org>,
linux-kernel@vger.kernel.org
Subject: Re: hundreds of mount --bind mountpoints?
Date: Mon, 23 Apr 2001 15:19:35 -0600 [thread overview]
Message-ID: <200104232119.f3NLJZT24922@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20010423224505.H719@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <20010423172335.G719@nightmaster.csn.tu-chemnitz.de> <Pine.GSO.4.21.0104231133120.3617-100000@weyl.math.psu.edu> <20010423224505.H719@nightmaster.csn.tu-chemnitz.de>
Ingo Oeser writes:
> On Mon, Apr 23, 2001 at 11:36:24AM -0400, Alexander Viro wrote:
> > > Great idea. We allocate this space anyway. And we don't have to
> > > care about the internals of this union, because never have to use
> > > it outside the kernel ;-)
> > >
> > > I like it. ext2fs does the same, so there should be no VFS
> > > hassles involved. Al?
> >
> > We should get ext2 and friends to move the sucker _out_ of struct inode.
> > As it is, sizeof(struct inode) is way too large. This is 2.5 stuff, but
> > it really has to be done. More filesystems adding stuff into the union
> > is a Bad Thing(tm). If you want to allocates space - allocate if yourself;
> > ->clear_inode() is the right place for freeing it.
>
> You need an inode anyway. So why not using the space in it? tmpfs
> would only use sizeof(*inode.u)-sizeof(struct shmem_inode_info) for
> this kind of symlinks.
>
> Last time we suggested this, people ended up with some OS trying
> it and getting worse performance.
>
> Why? You need to allocate the VFS-inode (vnode in other OSs) and
> the on-disk-inode anyway at the same time. You get better
> performance and less fragmentation, if you allocate them both
> together[1].
We want to take out that union because it sucks for virtual
filesystems. Besides, it's ugly.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-04-23 21:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 16:32 David L. Parsley
2001-04-22 16:41 ` Alexander Viro
2001-04-23 11:43 ` Christoph Rohland
2001-04-23 13:17 ` Ingo Oeser
2001-04-23 14:54 ` Christoph Rohland
2001-04-23 15:23 ` Ingo Oeser
2001-04-23 15:36 ` Alexander Viro
2001-04-23 20:45 ` Ingo Oeser
2001-04-23 20:56 ` Christoph Hellwig
2001-04-23 22:00 ` Ingo Oeser
2001-04-23 22:10 ` Alexander Viro
2001-04-23 22:47 ` Andreas Dilger
2001-04-24 1:37 ` Jan Harkes
2001-04-24 2:53 ` Alexander Viro
2001-04-24 9:58 ` David Woodhouse
2001-04-24 10:07 ` Alexander Viro
2001-04-24 10:19 ` David Woodhouse
2001-04-24 10:35 ` Christoph Rohland
2001-04-24 10:54 ` Alexander Viro
2001-04-24 12:51 ` David Woodhouse
2001-04-24 13:34 ` Christoph Rohland
2001-04-24 16:52 ` David L. Parsley
2001-05-05 7:48 ` [Patch] inline symlinks for tmpfs Christoph Rohland
2001-05-04 19:17 ` [Patch] encapsulate shmem access to shmem_inode_info Christoph Rohland
[not found] ` <3AF405FC.11D37FEB@bellsouth.net>
2001-05-06 13:58 ` [Resend] Collection of tmpfs patches Christoph Rohland
2001-04-24 16:04 ` Can't read SCSI TAPE Masaki Tsuji
2001-04-24 18:36 ` hundreds of mount --bind mountpoints? Andreas Dilger
2001-04-24 18:49 ` Alexander Viro
2001-04-24 19:11 ` Andreas Dilger
2001-04-24 22:01 ` Ingo Oeser
2001-04-24 21:59 ` Trond Myklebust
2001-04-24 22:09 ` Alexander Viro
2001-04-24 22:31 ` Trond Myklebust
2001-04-23 21:19 ` Richard Gooch [this message]
2001-04-23 22:42 ` Albert D. Cahalan
2001-04-23 22:49 ` Richard Gooch
2001-04-23 23:07 ` Alexander Viro
2001-04-23 23:24 ` Rik van Riel
2001-04-23 23:13 ` Richard Gooch
2001-04-24 6:33 ` Christoph Rohland
2001-04-23 14:08 ` David L. Parsley
2001-04-23 14:14 ` Alexander Viro
2001-04-24 0:16 Ed Tomlinson
2001-04-24 3:56 ` Andreas Dilger
2001-04-24 10:01 ` Alexander Viro
2001-04-24 13:27 ` Erik Mouw
2001-04-24 18:47 ` Andreas Dilger
2001-04-24 18:52 ` Alexander Viro
2001-04-24 20:45 ` Erik Mouw
2001-04-25 7:25 ` Christoph Rohland
2001-04-25 18:39 ` Andreas Dilger
2001-04-25 18:47 ` Alexander Viro
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=200104232119.f3NLJZT24922@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=cr@sap.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=parsley@linuxjedi.org \
--cc=viro@math.psu.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®