From: Christoph Rohland <cr@sap.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
"David L. Parsley" <parsley@linuxjedi.org>,
linux-kernel@vger.kernel.org
Subject: Re: hundreds of mount --bind mountpoints?
Date: 24 Apr 2001 08:33:12 +0200 [thread overview]
Message-ID: <m33dazqr86.fsf@linux.local> (raw)
In-Reply-To: <Pine.GSO.4.21.0104231133120.3617-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0104231133120.3617-100000@weyl.math.psu.edu>
Hi Alexander,
On Mon, 23 Apr 2001, Alexander Viro wrote:
>> 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.
Yes, I agree that the union is way too large and I did not plan to
extend it but simply use the size it has.
if (strlen(path) < sizeof(inode->u))
inline the symlink;
else
put it into the page cache;
So if somebody really cleans up the private inode structures it will
not trigger that often any more and we perhaps have to rethink the
idea.
But also if we use struct shmem_inode_info which is 92 bytes right now
we would inline all symlinks on my machine.
If we reduced its size to 32 (which could be easily done) we would
still inline 6642 out of 9317 symlinks on my machine. That's not bad.
Greetings
Christoph
next prev parent reply other threads:[~2001-04-24 6:51 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 16:32 hundreds of mount --bind mountpoints? 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 21:19 ` Richard Gooch
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:13 ` Richard Gooch
2001-04-23 23:24 ` Rik van Riel
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-24 6:33 ` Christoph Rohland [this message]
2001-04-23 14:08 ` David L. Parsley
2001-04-23 14:14 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
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=m33dazqr86.fsf@linux.local \
--to=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