From: Nix <nix@esperi.org.uk>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Chris Lightfoot <chris@ex-parrot.com>
Subject: Re: [uml-devel] When /tmp is not tmpfs.
Date: Fri, 25 Nov 2005 19:33:49 +0000 [thread overview]
Message-ID: <87k6ewikte.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200511251003.42328.rob@landley.net> (Rob Landley's message of "Fri, 25 Nov 2005 10:03:42 -0600")
On Fri, 25 Nov 2005, Rob Landley uttered the following:
> A) mlock would be a bad thing. Not only is it a trivial DOS waiting to happen
> but I like the UML physmem being swapped out under memory pressure. I just
> don't want uselessly writing it to disk over and over in the absence of any
> memory pressure whatosever to consume all I/O bandwidth to no purpose, which
> is the effect when it's not on tmpfs.
Maybe this is a stupid question, but... why do *any* systems other than
extremely memory-constrained ones not mount tmpfs on /tmp? It seems to
me to have numerous advantages and no disadvantages.
In fact, even when you're memory-constrained, if you *have* diskspace that
you could spend on /tmp, you can swap to it instead, and spend the space
on virtual memory when you're not spending it on /tmp.
So, er, why?
--
`Y'know, London's nice at this time of year. If you like your cities
freezing cold and full of surly gits.' --- David Damerell
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-25 19:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 12:11 [uml-devel] When /tmp is not tmpfs Rob Landley
2005-11-24 20:40 ` Blaisorblade
2005-11-25 8:26 ` Rob Landley
2005-11-25 9:55 ` Jeff Dike
2005-11-25 9:48 ` Rob Landley
2005-11-25 10:52 ` Rob Landley
2005-11-25 11:26 ` Rob Landley
2005-11-25 14:56 ` Nix
2005-11-25 15:03 ` Chris Lightfoot
2005-11-25 15:36 ` Nix
2005-11-25 16:03 ` Rob Landley
2005-11-25 19:33 ` Nix [this message]
2005-11-25 20:18 ` Rob Landley
2005-11-25 21:04 ` Nix
2005-11-25 22:31 ` Rob Landley
2005-11-27 16:48 ` Blaisorblade
2005-11-27 18:17 ` Nix
2005-11-27 19:24 ` Rob Landley
2005-11-25 23:33 ` Blaisorblade
2005-11-26 2:12 ` Nix
2005-11-26 11:47 ` Rob Landley
2005-11-27 17:37 ` Blaisorblade
2005-11-27 18:35 ` Nix
2005-11-27 19:10 ` Blaisorblade
2005-11-27 19:43 ` Nix
2005-11-27 21:21 ` Rob Landley
2005-11-27 18:59 ` Rob Landley
2005-11-27 19:20 ` Blaisorblade
2005-11-27 21:41 ` Rob Landley
2005-11-29 16:52 ` Blaisorblade
2005-11-27 18:31 ` Nix
2005-11-28 1:07 ` Rob Landley
2005-11-29 16:08 ` Blaisorblade
2005-11-29 19:38 ` Rob Landley
2005-11-26 10:44 ` Rob Landley
2005-11-27 16:38 ` Blaisorblade
2005-11-27 18:49 ` Nix
2005-11-27 21:25 ` Rob Landley
2005-11-27 17:10 ` Blaisorblade
2005-11-25 23:46 ` Chris Lightfoot
2005-11-26 10:03 ` Rob Landley
2005-11-26 10:15 ` Chris Lightfoot
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=87k6ewikte.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=chris@ex-parrot.com \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.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.