From: Christoph Rohland <cr@sap.com>
To: Daniel Egger <degger@fhm.edu>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: allow percentile size of tmpfs (2.5.66 / 2.4.20-pre2)
Date: Wed, 02 Apr 2003 09:13:39 +0200 [thread overview]
Message-ID: <ovfzp1l6cc.fsf@sap.com> (raw)
In-Reply-To: <1049221575.7628.14.camel@localhost> (Daniel Egger's message of "01 Apr 2003 20:26:15 +0200")
Hi Daniel,
On 01 Apr 2003, Daniel Egger wrote:
> Just curious: Why? I'm using tmpfs on these systems and I'm rather
> satisfied with it; especially the option to limit the amount of
> space makes it rather useful. According to the documentation ramfs
> is most useful as an educational example how to write filesystems
> not as a real filesystem...
Uuh, now you are beating me with my old statements ;-)
tmpfs has the drawback that the in memory data structures are bigger
than ramfs'. But the core of tmpfs is always compiled in for anonymous
shared memory. And it has size limits. So you are probably right, that
tmpfs is the right choice.
But you are arguing at a corner case. tmpfs is IMHO more often used on
machines with swap and (at least for me) the use of swap as store for
temporary data is the big point to use tmpfs. So the percentile should
take swap into account.
Greetings
Christoph
next prev parent reply other threads:[~2003-04-02 7:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 14:22 PATCH: allow percentile size of tmpfs (2.5.66 / 2.4.20-pre2) Mikael Starvik
2003-04-01 16:24 ` Christoph Rohland
2003-04-01 18:26 ` Daniel Egger
2003-04-01 19:25 ` Hugh Dickins
2003-04-01 19:57 ` Daniel Egger
2003-04-02 7:13 ` Christoph Rohland [this message]
2003-04-02 7:55 ` Hua Zhong
2003-04-02 10:26 ` Hugh Dickins
2003-04-03 2:49 ` Robert White
2003-04-03 2:54 ` Hua Zhong
[not found] <fa.eagpkml.m3elbd@ifi.uio.no>
2003-04-01 13:38 ` Ed Tomlinson
2003-04-01 14:17 ` Hugh Dickins
2003-04-01 14:18 ` CaT
2003-04-01 16:27 ` Christoph Rohland
2003-04-01 16:45 ` Hugh Dickins
2003-04-02 7:20 ` Christoph Rohland
2003-04-02 8:12 ` William Lee Irwin III
2003-04-02 14:44 ` CaT
2003-04-02 17:33 ` Christoph Rohland
2003-04-02 20:44 ` Jörn Engel
2003-04-02 21:04 ` Hugh Dickins
2003-04-03 7:44 ` Jörn Engel
2003-04-07 8:32 ` Christoph Rohland
2003-04-07 11:55 ` Hugh Dickins
2003-04-07 11:59 ` Christoph Rohland
2003-04-04 11:31 ` Henning P. Schmiedehausen
2003-04-03 5:35 ` CaT
2003-04-03 10:42 ` CaT
2003-04-02 10:04 ` Jörn Engel
2003-04-03 2:54 ` Robert White
2003-04-03 8:35 ` Hugh Dickins
2003-04-03 20:55 ` Robert White
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 8:10 CaT
2003-04-01 10:59 ` Xavier Bestel
2003-04-01 11:11 ` Hugh Dickins
2003-04-01 14:23 ` CaT
2003-04-01 14:43 ` Hugh Dickins
2003-04-01 14:54 ` CaT
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=ovfzp1l6cc.fsf@sap.com \
--to=cr@sap.com \
--cc=degger@fhm.edu \
--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