From: Minchan Kim <minchan.kim@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>, Johannes Weiner <hannes@cmpxchg.org>,
Wu Fengguang <fengguang.wu@intel.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>, Jens Axboe <axboe@kernel.dk>,
linux-mm@kvack.org
Subject: Re: [patch] mm: fix deferred congestion timeout if preferred zone is not allowed
Date: Thu, 20 Jan 2011 09:59:03 +0900 [thread overview]
Message-ID: <AANLkTi=UDM5bjOS+51CHRDMcouT6Q9kEaRxCJL4TS2gN@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101191212090.19519@chino.kir.corp.google.com>
On Thu, Jan 20, 2011 at 5:18 AM, David Rientjes <rientjes@google.com> wrote:
> On Wed, 19 Jan 2011, Andi Kleen wrote:
>
>> cpusets didn't exist when I designed that. But the idea was that
>> the kernel has a first choice ("hit") and any other node is a "miss"
>> that may need investigation. So yes I would consider cpuset config as an
>> intention too and should be counted as hit/miss.
>>
>
> Ok, so there's no additional modification that needs to be made with the
> patch (other than perhaps some more descriptive documentation of a
> NUMA_HIT and NUMA_MISS). When the kernel passes all zones into the page
> allocator, it's relying on cpusets to reduce that zonelist to only
> allowable nodes by using ALLOC_CPUSET. If we can allocate from the first
> zone allowed by the cpuset, it will be treated as a hit; otherwise, it
> will be treated as a miss. That's better than treating everything as a
> miss when the cpuset doesn't include the first node.
>
Thanks for the care on this issue, David, Christoph, Andi.
Looks good to me.
Feel free to add my Reviewed-by.
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
--
Kind regards,
Minchan Kim
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-20 0:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 5:09 David Rientjes
2011-01-18 6:04 ` KOSAKI Motohiro
2011-01-18 10:29 ` Mel Gorman
2011-01-19 12:48 ` KOSAKI Motohiro
2011-01-18 10:15 ` Mel Gorman
2011-01-18 20:24 ` David Rientjes
2011-01-18 20:42 ` Mel Gorman
2011-01-19 1:51 ` David Rientjes
2011-01-19 13:01 ` KOSAKI Motohiro
2011-01-19 18:37 ` David Rientjes
2011-01-19 12:52 ` KOSAKI Motohiro
2011-01-19 0:43 ` Minchan Kim
2011-01-19 1:53 ` David Rientjes
2011-01-19 4:10 ` Minchan Kim
2011-01-19 19:59 ` Christoph Lameter
2011-01-19 20:06 ` Andi Kleen
2011-01-19 20:18 ` David Rientjes
2011-01-19 23:07 ` Christoph Lameter
2011-01-20 0:59 ` Minchan Kim [this message]
2011-01-23 22:30 ` [patch v2] " David Rientjes
2011-01-24 17: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='AANLkTi=UDM5bjOS+51CHRDMcouT6Q9kEaRxCJL4TS2gN@mail.gmail.com' \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=axboe@kernel.dk \
--cc=cl@linux.com \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=rientjes@google.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