public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Kreen <marko@l-t.ee>
To: Bjorn Wesen <bjorn@sparta.lu.se>
Cc: Padraig Brady <padraig@antefacto.com>, linux-kernel@vger.kernel.org
Subject: Re: ramdisk/tmpfs/ramfs/memfs ?
Date: Thu, 26 Apr 2001 22:39:50 +0200	[thread overview]
Message-ID: <20010426223950.C3683@l-t.ee> (raw)
In-Reply-To: <3AE879AE.387D3B78@antefacto.com> <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se>
In-Reply-To: <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se>; from bjorn@sparta.lu.se on Thu, Apr 26, 2001 at 08:48:26PM +0200

On Thu, Apr 26, 2001 at 08:48:26PM +0200, Bjorn Wesen wrote:
> On Thu, 26 Apr 2001, Padraig Brady wrote:
> > 3. If I've no backing store (harddisk?) is there any advantage 
> >    of using tmpfs instead of ramfs? Also does tmpfs need a 
> >    backing store?
> 
> I don't know what tmpfs does actually, but if it is like you suggest (a
> ramfs that can be swapped out ?) then you don't need it obviously (since
> you don't have any swap).
> 
> ramfs simply inserts any files written into the kernels cache and tells it
> not to forget it. it can't get much more simple than that.
> 
> > 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

tmpfs is basically ramfs with limits.

-- 
marko


  reply	other threads:[~2001-04-26 20:59 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 [this message]
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
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=20010426223950.C3683@l-t.ee \
    --to=marko@l-t.ee \
    --cc=bjorn@sparta.lu.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox