public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: RaXl NXXez de Arenas Coronado <raul@viadomus.com>
Cc: linux-kernel@vger.kernel.org, rml@tech9.net
Subject: Re: Is /dev/shm needed?
Date: 17 Dec 2001 09:34:04 +0100	[thread overview]
Message-ID: <m38zc2i6tf.fsf@linux.local> (raw)
In-Reply-To: <E16FtLQ-00006A-00@DervishD.viadomus.com>
In-Reply-To: <E16FtLQ-00006A-00@DervishD.viadomus.com>

Hi Raúl,

On Mon, 17 Dec 2001, RaXl NXXez de Arenas Coronado wrote:
>>When one of these gets full I can either stop the affending job or
>>increase the limit
> 
>     That's one of my doubts: if the available RAM decreases then the
> buffer (disk) cache will do too. So, if I have /tmp mounted with
> tmpfs, the contents here will be cached no matter the available RAM,
> or am I completely wrong?

No, it will be swapped out.

Greetings
		Christoph



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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17  8:41 Is /dev/shm needed? RaúlNúñez de Arenas Coronado
2001-12-17  8:34 ` Christoph Rohland [this message]
  -- strict thread matches above, loose matches on Subject: below --
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 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 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=m38zc2i6tf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox