public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <padraig@antefacto.com>
To: 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 17:30:21 +0000	[thread overview]
Message-ID: <3C051F2D.2030804@antefacto.com> (raw)
In-Reply-To: <m3y9kqon6w.fsf@linux.local>

Christoph Rohland wrote:

> Hi,
> 
> Apparently there is a lack of information about tmpfs out there.


I aggree, and ramfs et al.


> So I would like to reduce the Configure.help entry and instead
> introduce a file Documentation/filesystems/tmpfs with more details.
> 
> My proposal is appended. Feedback about content and english language
> is highly appreciated.
> 
> Greetings
> 		Christoph
> 
> ------------------------------------------------------------------------
> 
> Tmpfs is a file system which keeps all files in virtual memory.
> 
> Everything is temporary in the sense that no files will be created on
> your hard drive. If you reboot, everything in tmpfs will be lost.
> 
> 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:


$ dd if=/dev/zero of=/tmp/use_mem bs=1024 count=20000
$ cat /proc/meminfo
         total:    used:    free:  shared: buffers:  cached:
Mem:  129966080 122720256  7245824    49152 65863680 28745728
Swap:        0        0        0
MemTotal:       126920 kB
MemFree:          7076 kB
MemShared:          48 kB
Buffers:         64320 kB
Cached:          28072 kB
SwapCached:          0 kB
Active:          10308 kB
Inact_dirty:     80196 kB
Inact_clean:      1936 kB
Inact_target:    26200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       126920 kB
LowFree:          7076 kB
SwapTotal:           0 kB
SwapFree:            0 kB

$ rm /tmp/use_mem
$ cat /proc/meminfo
         total:    used:    free:  shared: buffers:  cached:
Mem:  129966080 101957632 28008448    49152 65863680  8290304
Swap:        0        0        0
MemTotal:       126920 kB
MemFree:         27352 kB
MemShared:          48 kB
Buffers:         64320 kB
Cached:           8096 kB
SwapCached:          0 kB
Active:          10352 kB
Inact_dirty:     60196 kB
Inact_clean:      1916 kB
Inact_target:    26200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       126920 kB
LowFree:         27352 kB
SwapTotal:           0 kB
SwapFree:            0 kB

Padraig.


  reply	other threads:[~2001-11-28 17:33 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 [this message]
2001-11-28 17:37   ` Christoph Rohland
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=3C051F2D.2030804@antefacto.com \
    --to=padraig@antefacto.com \
    --cc=cr@sap.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