From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: cl@linux-foundation.org, narayanan.g@samsung.com,
kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: Performance degradation seen after using one list for hot/coldpages.
Date: Wed, 8 Jul 2009 14:32:01 -0700 [thread overview]
Message-ID: <20090708143201.efb67493.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090708152755.GC14601@csn.ul.ie>
> On Wed, 8 Jul 2009 16:27:55 +0100 Mel Gorman <mel@csn.ul.ie> wrote:
> There are a number of patches that
> I don't believe have made it upstream or into mmotm but I've lost track
> of what is in flight and what isn't. When an mmotm against 2.6.31-rc2 is
> out, I'll be going through it again to see what made it in and resending
> patches as appropriate.
I appear to be stuck in the wrong country again and won't be very
functional until next week, sorry. As usual, resending stuff doesn't hurt,
especially when that stuff was buried in the middle of a long email trail
under a quite different Subject:.
--
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>
prev parent reply other threads:[~2009-07-08 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 11:32 Re: Re: Performance degradation seen after using one list for hot/cold pages NARAYANAN GOPALAKRISHNAN
2009-06-22 16:52 ` Mel Gorman
2009-06-23 0:06 ` KAMEZAWA Hiroyuki
2009-06-23 17:41 ` Christoph Lameter
2009-06-25 9:11 ` Minchan Kim
2009-06-29 9:15 ` Mel Gorman
2009-07-08 2:37 ` Performance degradation seen after using one list for hot/coldpages Narayanan Gopalakrishnan
2009-07-08 14:53 ` Christoph Lameter
2009-07-08 15:27 ` Mel Gorman
2009-07-08 21:32 ` Andrew Morton [this message]
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=20090708143201.efb67493.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=narayanan.g@samsung.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 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.