From: Christoph Rohland <cr@sap.com>
To: Padraig Brady <padraig@antefacto.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ramdisk/tmpfs/ramfs/memfs ?
Date: 27 Apr 2001 09:58:47 +0200 [thread overview]
Message-ID: <m31yqeojt4.fsf@linux.local> (raw)
In-Reply-To: <3AE879AE.387D3B78@antefacto.com>
In-Reply-To: <3AE879AE.387D3B78@antefacto.com>
Hi Padraig,
On Thu, 26 Apr 2001, Padraig Brady wrote:
> 2. Is tmpfs is basically swap and /tmp together in a ramdisk?
> The advantage being you need to reserve less RAM for both
> together than seperately?
tmpfs is ramfs+swap+limits. It is not using ramdisks and is not
related to them.
> 3. If I've no backing store (harddisk?) is there any advantage
> of using tmpfs instead of ramfs? Also does tmpfs need a
> backing store?
Probably yes, since you spare a little bit kernel memory. most of
tmpfs is unconditionally in the kernel for shared mappings. So the
actual CONFIG_TMPFS only adds some small functions to the kernel to
export this to usre space.
Greetings
Christoph
prev parent reply other threads:[~2001-04-27 8:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 19:40 ramdisk/tmpfs/ramfs/memfs ? Padraig Brady
2001-04-26 18:48 ` Bjorn Wesen
2001-04-26 20:39 ` Marko Kreen
2001-04-27 0:37 ` H. Peter Anvin
2001-04-27 11:32 ` mirabilos
2001-04-27 13:41 ` Christoph Rohland
2001-04-26 20:49 ` H. Peter Anvin
2001-04-26 22:25 ` Ingo Oeser
2001-04-27 9:36 ` David Woodhouse
2001-04-27 11:36 ` mirabilos
2001-06-22 8:15 ` Padraig Brady
2001-04-27 15:56 ` David Woodhouse
2001-04-27 16:19 ` mirabilos
2001-04-27 17:39 ` David L. Parsley
2001-04-27 17:53 ` Padraig Brady
2001-04-27 17:23 ` Xavier Bestel
2001-04-28 10:30 ` David Woodhouse
2001-04-27 16:23 ` Padraig Brady
2001-04-27 14:31 ` Bjorn Wesen
2001-04-27 15:38 ` Christoph Rohland
2001-04-27 7:58 ` Christoph Rohland [this message]
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=m31yqeojt4.fsf@linux.local \
--to=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig@antefacto.com \
/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.