From: Christoph Rohland <cr@sap.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: 16 May 2001 16:43:37 +0200 [thread overview]
Message-ID: <m3wv7h5p7q.fsf@linux.local> (raw)
In-Reply-To: <Pine.GSO.4.21.0105160756210.24199-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105160756210.24199-100000@weyl.math.psu.edu>
Hi Al,
On Wed, 16 May 2001, Alexander Viro wrote:
> One point that might be better done differently - since we
> need ramfs for boot I've just made fs/Config.in declare CONFIG_RAMFS
> as define_bool CONFIG_RAMFS y. If ramfs grows (e.g. gets resource
> limits patches from -ac) we might be better off doing a minimal
> variant permanently in kernel (calling it rootfs) and making
> ramfs use rootfs methods. It's completely separate issue, so I've
> done it the simplest way for the time being.
Why do you use ramfs? Most of it is duplicated in tmpfs and ramfs is a
minimal _example_ fs. There was some agreement that this should stay
so.
Look into mm/shmem.c and look how little is added by CONFIG_TMPFS and
how much is duplicated from ramfs
If we really think the added swap vector per file in tmpfs is a major
overhead we should add the nonswapping functions there.
Greetings
Christoph
next prev parent reply other threads:[~2001-05-16 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 12:12 Alexander Viro
2001-05-16 14:43 ` Christoph Rohland [this message]
2001-05-16 18:23 ` Alexander Viro
2001-05-16 19:47 ` Christoph Rohland
2001-05-16 23:37 ` Alan Cox
2001-05-16 17:11 ` Linus Torvalds
2001-05-16 17:45 ` Christoph Rohland
2001-05-16 17:55 ` Jeff Garzik
2001-05-16 18:00 ` Linus Torvalds
2001-05-16 18:23 ` David L. Parsley
2001-05-16 18:46 ` Christoph Rohland
2001-05-16 18:33 ` Alexander Viro
2001-05-16 23:49 ` Alan Cox
2001-05-17 6:46 ` Christoph Rohland
2001-05-16 18:48 ` Alexander Viro
2001-05-16 22:21 ` H. Peter Anvin
2001-05-16 23:06 ` Alexander Viro
2001-05-16 23:24 ` H. Peter Anvin
2001-05-16 23:31 ` Alexander Viro
2001-05-16 23:33 ` Alan Cox
2001-05-17 0:10 ` 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=m3wv7h5p7q.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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®