From: Christoph Rohland <cr@sap.com>
To: Padraig Brady <padraig@antefacto.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Documentation/filesystems/tmpfs
Date: 28 Nov 2001 18:37:46 +0100 [thread overview]
Message-ID: <m3u1veokyd.fsf@linux.local> (raw)
In-Reply-To: <m3y9kqon6w.fsf@linux.local> <3C051F2D.2030804@antefacto.com>
In-Reply-To: <3C051F2D.2030804@antefacto.com>
Hi Padraig,
On Wed, 28 Nov 2001, Padraig Brady wrote:
>> 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?
> $ dd if=/dev/zero of=/tmp/use_mem bs=1024 count=20000
On what filesystem is /tmp/use_mem located? What do you want to show?
Greetings
Christoph
next prev parent reply other threads:[~2001-11-28 17:42 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 [this message]
2001-11-28 17:49 ` Padraig Brady
2001-11-28 20:38 ` [MOc]cda*mirabilos
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=m3u1veokyd.fsf@linux.local \
--to=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