public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "[MOc]cda*mirabilos" <mirabilos@netcologne.de>
To: "Padraig Brady" <padraig@antefacto.com>,
	"Christoph Rohland" <cr@sap.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Documentation/filesystems/tmpfs
Date: Wed, 28 Nov 2001 20:38:25 -0000	[thread overview]
Message-ID: <003101c1784c$a19aaa00$25aefea9@ecce> (raw)
In-Reply-To: <m3y9kqon6w.fsf@linux.local> <3C051F2D.2030804@antefacto.com> <m3u1veokyd.fsf@linux.local> <3C05238C.5080903@antefacto.com>

> >>>In contrast to RAM disks, which get allocated a fixed amount of
> >>>physical RAM, tmpfs grows and shrinks to accommodate the files it
> >>>contains and is able to swap unneeded pages out to swap space.
> >>That isn't the case now since ramdisks were integrated with the
> >>buffer cache:
> > What isn't the case any more?
> Because the RAM is now (de)allocated as required.
> Filesystem? ext2 on /dev/ram1(rd.o)
> meminfo shows the memory being reclaimed as the file is deleted.

And this is transparent to {any|the ext2fs} underlying filesystem?
What if I use xfs, rasierfs, ntfs, $* ?

-mirabilos
-- 
Redistribution of this message body via AOL or the
Microsoft network strictly prohibited.
Quotation permitted if due credit is given.
(Excuse the X-Mailer, accusate my ISP for that)



      reply	other threads:[~2001-11-28 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 16:49 [RFC] Documentation/filesystems/tmpfs Christoph Rohland
2001-11-28 17:30 ` Padraig Brady
2001-11-28 17:37   ` Christoph Rohland
2001-11-28 17:49     ` Padraig Brady
2001-11-28 20:38       ` [MOc]cda*mirabilos [this message]

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='003101c1784c$a19aaa00$25aefea9@ecce' \
    --to=mirabilos@netcologne.de \
    --cc=cr@sap.com \
    --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