From: "Martin J. Bligh" <mbligh@google.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [RFC] Remove temp_priority
Date: Wed, 18 Oct 2006 07:47:02 -0700 [thread overview]
Message-ID: <45363E66.8010201@google.com> (raw)
In-Reply-To: <45362130.6020804@yahoo.com.au>
> Coming from another angle, I am thinking about doing away with direct
> reclaim completely. That means we don't need any GFP_IO or GFP_FS, and
> solves the problem of large numbers of processes stuck in reclaim and
> skewing aging and depleting the memory reserve.
Last time I proposed that, the objection was how to throttle the heavy
dirtiers so they don't fill up RAM with dirty pages?
Also, how do you do atomic allocations? Create a huge memory pool and
pray really hard?
> But that's tricky because we don't have enough kswapds to get maximum
> reclaim throughput on many configurations (only single core opterons
> and UP systems, really).
It's not a question of enough kswapds. It's that we can dirty pages
faster than they can possibly be written to disk.
dd if=/dev/zero of=/tmp/foo
M.
WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <mbligh@google.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [RFC] Remove temp_priority
Date: Wed, 18 Oct 2006 07:47:02 -0700 [thread overview]
Message-ID: <45363E66.8010201@google.com> (raw)
In-Reply-To: <45362130.6020804@yahoo.com.au>
> Coming from another angle, I am thinking about doing away with direct
> reclaim completely. That means we don't need any GFP_IO or GFP_FS, and
> solves the problem of large numbers of processes stuck in reclaim and
> skewing aging and depleting the memory reserve.
Last time I proposed that, the objection was how to throttle the heavy
dirtiers so they don't fill up RAM with dirty pages?
Also, how do you do atomic allocations? Create a huge memory pool and
pray really hard?
> But that's tricky because we don't have enough kswapds to get maximum
> reclaim throughput on many configurations (only single core opterons
> and UP systems, really).
It's not a question of enough kswapds. It's that we can dirty pages
faster than they can possibly be written to disk.
dd if=/dev/zero of=/tmp/foo
M.
--
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>
next prev parent reply other threads:[~2006-10-18 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 17:34 [RFC] Remove temp_priority Martin Bligh
2006-10-17 17:42 ` Nick Piggin
2006-10-17 17:42 ` Nick Piggin
2006-10-17 17:52 ` Martin Bligh
2006-10-17 17:52 ` Martin Bligh
2006-10-18 12:42 ` Nick Piggin
2006-10-18 12:42 ` Nick Piggin
2006-10-18 14:47 ` Martin J. Bligh [this message]
2006-10-18 14:47 ` Martin J. Bligh
2006-10-18 14:56 ` Nick Piggin
2006-10-18 14:56 ` Nick Piggin
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=45363E66.8010201@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=npiggin@suse.de \
/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.