public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: "RaúlNúñez de Arenas Coronado" <raul@viadomus.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is /dev/shm needed?
Date: 16 Dec 2001 17:30:47 -0500	[thread overview]
Message-ID: <1008541849.11242.2.camel@phantasy> (raw)
In-Reply-To: <E16FjME-0000WW-00@DervishD.viadomus.com>
In-Reply-To: <E16FjME-0000WW-00@DervishD.viadomus.com>

On Sun, 2001-12-16 at 17:02, RaúlNúñez de Arenas Coronado wrote:

>     I don't know if /dev/shm (mounted with shmfs or the newer tmpfs)
> is needed for proper SYSV IPC operation with newer (2.4.16 and newer)
> kernel. Anyone can help?

It is not needed.  /dev/shm mounted with tmpfs is only needed for POSIX
shared memory, which is still fairly rare.  SysV IPC will work fine.

>     Moreover: I want to move my /tmp from disk to tmpfs for speed (I
> make a lot of compiling, so I think it would help). Is this a good
> idea? If so, what size can be appropriate for a small system that is
> not permanently running?

Some say it helps, others don't.  Solaris has a similar feature, and it
seems to work for them.  However, Linux is light and our page-cache
works well.  Not so sure it is ideal.

In other words, if you have memory to spare and the data ought to be
cached, Linux probably will cache it anyhow.  On the other hand, if you
have lots of memory to spare, give it a try.  Mount /tmp or all of /var
in tmpfs.

It is dynamic, so you don't need to specify a size.  If you want to give
a maximum size (probably a good idea), give one.  Depends on what your
tmp usages are and how much free memory you have.

	Robert Love


  reply	other threads:[~2001-12-16 22:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 22:02 Is /dev/shm needed? RaúlNúñez de Arenas Coronado
2001-12-16 22:30 ` Robert Love [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-12-16 23:15 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
2001-12-16 23:36 RaúlNúñez de Arenas Coronado
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-17  4:14 Jason Rivard
2001-12-17  8:41 RaúlNúñez de Arenas Coronado
2001-12-17  8:34 ` 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=1008541849.11242.2.camel@phantasy \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@viadomus.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