From: Christoph Rohland <cr@sap.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch?] RAMFS
Date: 04 Feb 2001 10:53:28 +0100 [thread overview]
Message-ID: <m3r91en5jj.fsf@linux.local> (raw)
In-Reply-To: <Pine.Linu.4.10.10102040713280.663-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10102040713280.663-100000@mikeg.weiden.de>
Mike Galbraith <mikeg@wen-online.de> writes:
> However, tmpfs appears to cover the functionality provided by ramfs.
> Are there any uses for ramfs which can't be handled by tmpfs?
Nothing I know of.
> The only thing I could think of was "what if you don't have a
> swap device up and running". Seems it doesn't need one :))
Yes and no. tmpfs has a little bit overhead for the noswap case but
this overhead is in the kernel anyways for shared anon mappings. The
whole vm is using swap unconditionally.
Greetings
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 19:02 [patch?] RAMFS Mike Galbraith
2001-02-04 6:32 ` Mike Galbraith
2001-02-04 9:53 ` Christoph Rohland [this message]
2001-02-04 13:48 ` David Woodhouse
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=m3r91en5jj.fsf@linux.local \
--to=cr@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.