From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ramdisk/tmpfs/ramfs/memfs ?
Date: 26 Apr 2001 13:49:05 -0700 [thread overview]
Message-ID: <9ca1k1$4ap$1@cesium.transmeta.com> (raw)
In-Reply-To: <3AE879AE.387D3B78@antefacto.com> <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se>
Followup to: <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se>
By author: Bjorn Wesen <bjorn@sparta.lu.se>
In newsgroup: linux.dev.kernel
>
> > 5. Can you set size limits on ramfs/tmpfs/memfs?
>
> i don't think you can set a limit in the current ramfs implementation but
> it would not be particularly difficult to make it work I think
>
It's a little more painful than you'd think for the simple reason that
ramfs currently contains no space accounting whatsoever, which
probably is a bad thing. It definitely gave me some serious pause
when I was working on SuperRescue 1.3, since I had no way of
reasonably judging how big my ramfs actually was. The only way I
could get a reasonable idea was rebooting with various mem=
parameters.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
next prev parent reply other threads:[~2001-04-26 20:49 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 [this message]
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='9ca1k1$4ap$1@cesium.transmeta.com' \
--to=hpa@zytor.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