From: Christoph Rohland <cr@sap.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>,
Alexander Viro <viro@math.psu.edu>,
Ed Tomlinson <tomlins@cam.org>,
linux-kernel@vger.kernel.org
Subject: Re: hundreds of mount --bind mountpoints?
Date: 25 Apr 2001 09:25:19 +0200 [thread overview]
Message-ID: <m3bspla1b4.fsf@linux.local> (raw)
In-Reply-To: <200104241847.f3OIlc7T016933@webber.adilger.int>
In-Reply-To: <200104241847.f3OIlc7T016933@webber.adilger.int>
Hi Andreas,
On Tue, 24 Apr 2001, Andreas Dilger wrote:
> On the other hand, sockets and shmem are both relatively large...
shmem is only large because the union is large. I introduced the
direct swap array of size SHMEM_NR_DIRECT simply to take advantage of
the union. We can decrease SHMEM_NR_DIRECT very easily. I am thinking
about 1 or 5 which would mean that we allocate an indirect block for
files bigger than 4k or 20k respectively.
The shmem_inode_info would then be 8 or 12 words.
Greetings
Christoph
next prev parent reply other threads:[~2001-04-25 7:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 0:16 hundreds of mount --bind mountpoints? 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 [this message]
2001-04-25 18:39 ` Andreas Dilger
2001-04-25 18:47 ` Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
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 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-04-24 18:36 ` 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
2001-04-23 14:08 ` David L. Parsley
2001-04-23 14:14 ` 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=m3bspla1b4.fsf@linux.local \
--to=cr@sap.com \
--cc=J.A.K.Mouw@its.tudelft.nl \
--cc=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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