From: Ed Tomlinson <tomlins@cam.org>
To: CaT <cat@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: PATCH: allow percentile size of tmpfs (2.5.66 / 2.4.20-pre2)
Date: Tue, 01 Apr 2003 08:38:32 -0500 [thread overview]
Message-ID: <20030401133833.6C71DF3D@oscar.casa.dyndns.org> (raw)
In-Reply-To: <fa.eagpkml.m3elbd@ifi.uio.no>
CaT wrote:
> I believe the patch below will apply to both the above (I know it does
> to 2.5.66 and 2.4.20-pre2 mm/shmem.c does not look any different so it
> should be fine. :)
>
> Anyways, what this patch does is allow you to specify the max amount of
> memory tmpfs can use as a percentage of available real ram. This (in my
> eyes) is useful so that you do not have to remember to change the
> setting if you want something other then 50% and some of your ram does
> (and you can't replacew it immediately).
>
> Usage of this option is as follows:
>
> tmpfs /dev/shm tmpfs rw,size=63%,noauto 0 0
>
> This is taken from my working system and sets the tmpfs size to 63% of
> my real RAM (256MB). The end result is:
>
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/shm/tmp 160868 6776 154092 5% /tmp
>
> I've also tested remounting to silly values (and sane ones) and it all
> works fine with no oopses or freezes and the correct values appearing
> in df.
>
> All up I feel safer using this then a hard value.
What does tmpfs have to do with ram size? Its swappable. This _might_ be
useful for ramfs but for tmpfs, IMHO, its not a good idea.
Ed Tomlinson
next parent reply other threads:[~2003-04-01 13:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.eagpkml.m3elbd@ifi.uio.no>
2003-04-01 13:38 ` Ed Tomlinson [this message]
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
2003-04-01 14:22 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
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
-- 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=20030401133833.6C71DF3D@oscar.casa.dyndns.org \
--to=tomlins@cam.org \
--cc=cat@zip.com.au \
--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
all inboxes | Powered by JetHome®