From: Padraig Brady <padraig@antefacto.com>
To: linux-kernel@vger.kernel.org
Subject: ramdisk/tmpfs/ramfs/memfs ?
Date: Thu, 26 Apr 2001 20:40:30 +0100 [thread overview]
Message-ID: <3AE879AE.387D3B78@antefacto.com> (raw)
Hi,
I'm working on an embedded system here which has no harddisk.
So, I can't swap to disk and need to have /var & /tmp in RAM.
I'm confused between the various options for in RAM file-
systems. At the moment I've created a ramdisk and made an
ext2 partition in it (which is compressed as I applied the
e2compr patch), which is working fine. Anyway questions:
1. I presume the kernel is clever enough to not cache any
files from these filesystems? Would it ever need to?
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?
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?
5. Can you set size limits on ramfs/tmpfs/memfs?
6. Is a ramdisk resizable like the others. If so, do you have
to delete/recreate or umount/resize a fs (e.g. ext2) every
time it's resized? Do ramfs/tmpfs/memfs do this transparently?
Are ramdisks resizable in kernel 2.2?
7. What's memfs?
8. Is there a way I can get transparent compression like I now
have using a ramdisk+ext2+e2compr with ramfs et al?
9. Apart from this transparent compression, is there any other
functionality ext2 would have over ramfs for e.g, for /tmp
& /var? Also would ramfs have less/more speed over ext2?
thanks,
Padraig.
next reply other threads:[~2001-04-26 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 19:40 Padraig Brady [this message]
2001-04-26 18:48 ` ramdisk/tmpfs/ramfs/memfs ? 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
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=3AE879AE.387D3B78@antefacto.com \
--to=padraig@antefacto.com \
--cc=linux-kernel@vger.kernel.org \
/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