public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: tomlins@cam.org, CaT <cat@zip.com.au>, <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: allow percentile size of tmpfs (2.5.66 / 2.4.20-pre2)
Date: Wed, 02 Apr 2003 09:20:50 +0200	[thread overview]
Message-ID: <ovd6k5l60d.fsf@sap.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304011734370.1503-100000@localhost.localdomain> (Hugh Dickins's message of "Tue, 1 Apr 2003 17:45:39 +0100 (BST)")

Hi Hugh,

On Tue, 1 Apr 2003, Hugh Dickins wrote:
> You surprise me, Christoph, I'd expected you to approve of CaT's.

look back into your mail store. I said this pretty early. 

> If tmpfs already defaulted to 50% of ram+swap, then I'd agree
> with you.  But it has all along been in terms of RAM, so I think
> it's better to continue in that way.  (We could add options to
> allow +swap in too, but I'm not terribly interested.)

No, I always thought the 50% RAM was a terrible hack. And IMHO it is
one of the biggest usability gaps of tmpfs. 

> If people really wanted their tmpfs pages to go out to disk, I think
> they'd be choosing a more sophisticated filesystem to manage that:
> swap is a vital overflow area for tmpfs, not its home.

I definitely want them to go there. It is a very sophisticated
mechinsm because by adding swap on _any_ storage I can grow my tmpfs
instances even temporarily.

If you now were able to take advantage of additional swap
automatically administration would be a no brainer. Also distributions
could add much saner defaults for /dev/shm or even use it for /tmp.

Greetings
		Christoph



  reply	other threads:[~2003-04-02  7:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.eagpkml.m3elbd@ifi.uio.no>
2003-04-01 13:38 ` PATCH: allow percentile size of tmpfs (2.5.66 / 2.4.20-pre2) Ed Tomlinson
2003-04-01 14:17   ` Hugh Dickins
2003-04-01 14:18   ` CaT
2003-04-01 16:27   ` Christoph Rohland
2003-04-01 16:45     ` Hugh Dickins
2003-04-02  7:20       ` Christoph Rohland [this message]
2003-04-02  8:12         ` William Lee Irwin III
2003-04-02 14:44         ` CaT
2003-04-02 17:33           ` Christoph Rohland
2003-04-02 20:44             ` Jörn Engel
2003-04-02 21:04               ` Hugh Dickins
2003-04-03  7:44                 ` Jörn Engel
2003-04-07  8:32                 ` Christoph Rohland
2003-04-07 11:55                   ` Hugh Dickins
2003-04-07 11:59                     ` Christoph Rohland
2003-04-04 11:31               ` Henning P. Schmiedehausen
2003-04-03  5:35             ` CaT
2003-04-03 10:42               ` CaT
2003-04-02 10:04     ` Jörn Engel
2003-04-03  2:54     ` Robert White
2003-04-03  8:35       ` Hugh Dickins
2003-04-03 20:55         ` Robert White
2003-04-01 14:22 Mikael Starvik
2003-04-01 16:24 ` Christoph Rohland
2003-04-01 18:26   ` Daniel Egger
2003-04-01 19:25     ` Hugh Dickins
2003-04-01 19:57       ` Daniel Egger
2003-04-02  7:13     ` Christoph Rohland
2003-04-02  7:55       ` Hua Zhong
2003-04-02 10:26         ` Hugh Dickins
2003-04-03  2:49         ` Robert White
2003-04-03  2:54           ` Hua Zhong
  -- strict thread matches above, loose matches on Subject: below --
2003-04-01  8:10 CaT
2003-04-01 10:59 ` Xavier Bestel
2003-04-01 11:11   ` Hugh Dickins
2003-04-01 14:23     ` CaT
2003-04-01 14:43       ` Hugh Dickins
2003-04-01 14:54         ` CaT

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=ovd6k5l60d.fsf@sap.com \
    --to=cr@sap.com \
    --cc=cat@zip.com.au \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlins@cam.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