From: Andrew Morton <akpm@linux-foundation.org>
To: Rik van Riel <riel@redhat.com>
Cc: clameter@sgi.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/10] split anon and file LRUs
Date: Wed, 7 Nov 2007 09:59:45 -0800 [thread overview]
Message-ID: <20071107095945.c9b870fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071106215127.29e90ecd@bree.surriel.com>
> On Tue, 6 Nov 2007 21:51:27 -0500 Rik van Riel <riel@redhat.com> wrote:
> On Tue, 6 Nov 2007 18:40:46 -0800 (PST)
> Christoph Lameter <clameter@sgi.com> wrote:
>
> > On Tue, 6 Nov 2007, Rik van Riel wrote:
> >
> > > Also, a factor 16 increase in page size is not going to help
> > > if memory sizes also increase by a factor 16, since we already
> > > have trouble with today's memory sizes.
> >
> > Note that a factor 16 increase usually goes hand in hand with
> > more processors. The synchronization of multiple processors becomes a
> > concern. If you have an 8p and each of them tries to get the zone locks
> > for reclaim then we are already in trouble. And given the immaturity
> > of the handling of cacheline contention in current commodity hardware this
> > is likely to result in livelocks and/or starvation on some level.
>
> Which is why we need to greatly reduce the number of pages
> scanned to free a page. In all workloads.
It strikes me that splitting one list into two lists will not provide
sufficient improvement in search efficiency to do that. I mean, a naive
guess would be that it will, on average, halve the amount of work which
needs to be done.
But we need multiple-orders-of-magnitude improvements to address the
pathological worst-cases which you're looking at there. Where is this
coming from?
Or is the problem which you're seeing due to scanning of mapped pages
at low "distress" levels?
Would be interested in seeing more details on all of this, please.
--
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:[~2007-11-07 17:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 22:42 Rik van Riel
2007-11-03 22:54 ` [RFC PATCH 1/10] move isolate_lru_page to vmscan.c Rik van Riel
2007-11-07 2:13 ` Christoph Lameter
2007-11-03 22:54 ` [RFC PATCH 2/10] free swap space entries if vm_swap_full() Rik van Riel
2007-11-07 2:20 ` Christoph Lameter
2007-11-07 2:48 ` Rik van Riel
2007-11-03 22:55 ` [RFC PATCH 3/10] define page_file_cache Rik van Riel
2007-11-07 2:23 ` Christoph Lameter
2007-11-07 2:55 ` Rik van Riel
2007-11-07 3:02 ` Christoph Lameter
2007-11-07 3:17 ` Rik van Riel
2007-11-07 3:26 ` Christoph Lameter
2007-11-07 14:35 ` Rik van Riel
2007-11-07 18:06 ` Christoph Lameter
2007-11-07 18:17 ` Rik van Riel
2007-11-07 18:18 ` Christoph Lameter
2007-11-03 22:55 ` [RFC PATCH 4/10] debug page_file_cache Rik van Riel
2007-11-03 22:56 ` [RFC PATCH 5/10] use an indexed array for LRU lists and variables Rik van Riel
2007-11-03 23:01 ` [RFC PATCH 6/10] split anon and file LRUs Rik van Riel
2007-11-07 2:28 ` Christoph Lameter
2007-11-07 3:00 ` Rik van Riel
2007-11-03 23:02 ` [RFC PATCH 7/10] clean up the LRU array arithmetic Rik van Riel
2007-11-03 23:03 ` [RFC PATCH 8/10] make split VM and lumpy reclaim work together Rik van Riel
2007-11-03 23:04 ` [RFC PATCH 9/10] split VM and memory controllers Rik van Riel
2007-11-03 23:06 ` [RFC PATCH 10/10] add swapped in pages to the inactive list Rik van Riel
2007-11-07 2:11 ` [RFC PATCH 0/10] split anon and file LRUs Christoph Lameter
2007-11-07 2:23 ` Rik van Riel
2007-11-07 2:40 ` Christoph Lameter
2007-11-07 2:51 ` Rik van Riel
2007-11-07 17:59 ` Andrew Morton [this message]
2007-11-07 18:16 ` 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=20071107095945.c9b870fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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