linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Aubrey Li <aubreylee@gmail.com>,
	Christoph Lameter <clameter@sgi.com>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Robin Getz <rgetz@blackfin.uclinux.org>,
	?missing, Michael <Michael.Hennerich@analog.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Limit the size of the pagecache
Date: Thu, 25 Jan 2007 15:51:34 +0100	[thread overview]
Message-ID: <E1HA5ws-0000vQ-KM@be1.lrz> (raw)
In-Reply-To: <7GRLZ-7Uy-29@gated-at.bofh.it>

Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Wed, 2007-01-24 at 22:22 +0800, Aubrey Li wrote:
>> On 1/24/07, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

>> > He wants to make a nommu system act like a mmu system; this will just
>> > never ever work.
>> 
>> Nope. Actually my nommu system works great with some of patches made by us.
>> What let you think this will never work?
> 
> Because there are perfectly valid things user-space can do to mess you
> up. I forgot the test-case but it had something to do with opening a
> million files, this will scatter slab pages all over the place.

a) Limit the number of open files.
b) Don't do that then.

> Also, if you cycle your large user-space allocations a bit unluckily
> you'll also fragment it into oblivion.
> 
> So you can not guarantee it will not fragment into smithereens stopping
> your user-space from using large than page size allocations.

Therefore you should purposely increase the mess up to the point where the
system is guaranteed not to work? IMO you should rather put the other issues
onto the TODO list.

BTW: I'm not sure a hard limit is the right thing to do for mmu systems,
I'd rather implement high and low watermarks; if one pool is larger than
it's high watermark, it will be next get it's pages evicted, and it won't
lose pages if it's at the lower watermark.

> If your user-space consists of several applications that do dynamic
> memory allocation of various sizes its a matter of (run-) time before
> things will start failing.
> 
> If you prealloc a large area at boot time (like we now do for hugepages)
> and use that for user-space, you might 'reset' the status quo by cycling
> the whole of userspace.

Preallocating the page cache (and maybe the slab space?) may very well be
the right thing to do for nommu systems. It worked quite well in DOS times
and on old MACs.
-- 
Funny quotes:
30. Why is a person who plays the piano called a pianist but a person who
    drives a race car not called a racist?
Friss, Spammer: iz@7eggert.dyndns.org pveUtv@rFGfMneI.7eggert.dyndns.org

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

       reply	other threads:[~2007-01-25 14:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7GEEK-4lH-39@gated-at.bofh.it>
     [not found] ` <7GLdb-5Uz-13@gated-at.bofh.it>
     [not found]   ` <7GRix-7fU-1@gated-at.bofh.it>
     [not found]     ` <7GRLZ-7Uy-29@gated-at.bofh.it>
2007-01-25 14:51       ` Bodo Eggert [this message]
2007-01-24  0:49 Christoph Lameter
2007-01-24  2:53 ` KAMEZAWA Hiroyuki
2007-01-24  3:01   ` Christoph Lameter
2007-01-24  5:47   ` Aubrey Li
2007-01-24  3:00 ` Nick Piggin
2007-01-24  3:14   ` Christoph Lameter
2007-01-24  3:51     ` Aubrey Li
2007-01-24  4:03       ` Nick Piggin
2007-01-26 10:27         ` Andrew Morton
2007-01-24  3:13 ` KAMEZAWA Hiroyuki
2007-01-24  4:30   ` Christoph Lameter
2007-01-24  5:15     ` KAMEZAWA Hiroyuki
2007-01-25  0:32       ` KAMEZAWA Hiroyuki
2007-01-25  2:41         ` Christoph Lameter
2007-01-25  3:12           ` KAMEZAWA Hiroyuki
2007-01-25  4:28             ` Rik van Riel
2007-01-25  5:19               ` KAMEZAWA Hiroyuki
2007-01-25  5:40                 ` Rik van Riel
2007-01-25  6:00                   ` KAMEZAWA Hiroyuki
2007-01-26 10:29       ` Andrew Morton
2007-01-26 18:01         ` KAMEZAWA Hiroyuki
2007-01-24  7:04 ` Vaidyanathan Srinivasan
2007-01-24  7:55 ` Peter Zijlstra
2007-01-24 12:50   ` Nick Piggin
2007-01-24 12:58     ` Peter Zijlstra
2007-01-24 14:58     ` Christoph Lameter
2007-01-24 20:06       ` Erik Andersen
2007-01-25  2:40         ` Christoph Lameter
2007-01-25  8:07           ` Vaidyanathan Srinivasan
2007-01-24 14:22   ` Aubrey Li
2007-01-24 14:56     ` Peter Zijlstra
2007-01-25  2:27       ` Aubrey Li
2007-01-24 12:33 ` Vaidyanathan Srinivasan
2007-01-24 14:56   ` Christoph Lameter
2007-01-25  4:17     ` Vaidyanathan Srinivasan
2007-01-25  4:45       ` Rik van Riel
2007-01-25  5:49         ` Vaidyanathan Srinivasan
2007-01-25 16:07           ` Rik van Riel
2007-01-25 17:57             ` Balbir Singh
2007-01-25  6:35       ` Aubrey Li
2007-01-25  6:47         ` Christoph Lameter
2007-01-25  7:49         ` Vaidyanathan Srinivasan
2007-01-25  4:18 ` Rik van Riel

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=E1HA5ws-0000vQ-KM@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=aubreylee@gmail.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=svaidy@linux.vnet.ibm.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