From: Christoph Rohland <cr@sap.com>
To: david+validemail@kalifornia.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: shmem or swapfs? was: [Patch] make shm filesystem part configurable
Date: 13 Jan 2001 15:04:41 +0100 [thread overview]
Message-ID: <m33denk0p2.fsf@linux.local> (raw)
In-Reply-To: <m366jj20si.fsf@linux.local> <3A604B26.53EC029F@linux.com>
In-Reply-To: <3A604B26.53EC029F@linux.com>
David Ford <david@linux.com> writes:
> Now...is this shared memory or swap? If it's swap, why is it
> different than a swapfile? If you are intending the shmem be called
> swapfs, I personally thing that it'll cause a significant amount of
> confusion.
It is a filesystem which lives in RAM and can swap out. SYSV shm and
shared anonymous maps are still build on top of this (The config
option only disables the part not needed for this).
I am quite open about naming, but "shm" is not appropriate any more
since the fs does a lot more than shared memory. Solaris calles this
"tmpfs" but I did not want to 'steal' their name and I also do not
think that it's a very good name.
So any suggestions for a better name?
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-01-13 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 10:49 [Patch] make shm filesystem part configurable Christoph Rohland
2001-01-13 12:33 ` shmem or swapfs? was: " David Ford
2001-01-13 14:04 ` Christoph Rohland [this message]
2001-01-13 14:16 ` David Ford
2001-01-13 16:51 ` Christoph Rohland
2001-01-13 22:39 ` David Ford
2001-01-13 20:14 ` Albert D. Cahalan
2001-01-14 9:56 ` Christoph Rohland
2001-01-14 13:56 ` James H. Cloos Jr.
[not found] ` <20010114134457.A14486@uni-mainz.de>
2001-01-14 21:29 ` Christoph Rohland
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 20:58 Dan Kegel
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=m33denk0p2.fsf@linux.local \
--to=cr@sap.com \
--cc=david+validemail@kalifornia.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