All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "RaúlNúñez de Arenas Coronado" <raul@viadomus.com>
Cc: rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: Is /dev/shm needed?
Date: 17 Dec 2001 09:19:01 +0100	[thread overview]
Message-ID: <m3heqqi7ii.fsf@linux.local> (raw)
In-Reply-To: <E16FkV9-00010E-00@DervishD.viadomus.com>
In-Reply-To: <E16FkV9-00010E-00@DervishD.viadomus.com>

Hi RaúlNúñez,

On Mon, 17 Dec 2001, RaúlNúñez de Arenas Coronado wrote:
>     Hello Robert :)
> 
>>It is not needed.  /dev/shm mounted with tmpfs is only needed for
>>POSIX shared memory, which is still fairly rare.
> 
>     That this means that I can mount more than one 'tmpfs' just like
> if it's a *real* filesystem? I wasn't sure, since it's implemented
> thru the page cache.

Yes, every single mount is an independant tree.

>>It is dynamic, so you don't need to specify a size.
> 
>     Yes, I knew, I meant the maximum size. I don't want half of the
> RAM occupied just by a programming mistake ;)))

What I like most about /tmp in tmpfs is the ability to resize on the
fly: I have a big swap partition and a reasonable limit for /tmp and
/var/tmp.

When one of these gets full I can either stop the affending job or
increase the limit: If there is swap left I can simply increase the
limit. If swap is full I add a swap file on a real filesystem and
increase the limit.

Greetings
		Christoph

P.S: Documentation/filesystems/tmpfs.txt is in the 2.4.17-rc patch.


  parent reply	other threads:[~2001-12-17  8:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 23:15 Is /dev/shm needed? RaúlNúñez de Arenas Coronado
2001-12-16 23:12 ` Robert Love
2001-12-16 23:31   ` Pierfrancesco Caci
2001-12-17  8:36     ` ncw
2001-12-17  8:19 ` Christoph Rohland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17  8:41 RaúlNúñez de Arenas Coronado
2001-12-17  8:34 ` Christoph Rohland
2001-12-17  4:14 Jason Rivard
2001-12-16 23:37 RaúlNúñez de Arenas Coronado
2001-12-16 23:47 ` Adam Schrotenboer
2001-12-16 23:56   ` Ryan Cumming
2001-12-17  0:17     ` Adam Schrotenboer
2001-12-17  2:26     ` H. Peter Anvin
2001-12-17 15:50 ` Luigi Genoni
2001-12-16 23:36 RaúlNúñez de Arenas Coronado
2001-12-16 22:02 RaúlNúñez de Arenas Coronado
2001-12-16 22:30 ` Robert Love
2001-12-16 23:13   ` Adam Schrotenboer
2001-12-16 23:26     ` J Sloan
2001-12-16 23:27   ` Alexander Viro
2001-12-17  9:03     ` Jurgen Botz

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=m3heqqi7ii.fsf@linux.local \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@viadomus.com \
    --cc=rml@tech9.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.