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 17:38:19 +0200 [thread overview]
Message-ID: <m3u23afj4k.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se> <3AE99CE8.BD325F52@antefacto.com>
In-Reply-To: <3AE99CE8.BD325F52@antefacto.com>
Hi Padraig,
On Fri, 27 Apr 2001, Padraig Brady wrote:
> I don't have swap so don't need tmpfs, but could probably
> use it anyway without a backing store?
Yes, it does not need backing store.
> Anyway why was ramfs created if tmpfs existed, unless tmpfs requires
> backing store? They both seem to have been written around the same
> time?
- shm fs was written as a specialized fs to implement POSIX shared
memory based on SYSV shm.
- ramfs was introduced shortly after shm fs and was meant as a
programming example for a minimal virtual filesystem.
- Later shm fs was redone to use the same methods like ramfs but still
was only useable for shared memory.
- After the release of 2.4.0, I extended shm fs to support read/write
and thus be tmpfs and since then it can replace ramfs.
Greetings
Christoph
next prev parent reply other threads:[~2001-04-27 15:43 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 [this message]
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=m3u23afj4k.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.