From: Andi Kleen <andi@firstfloor.org>
To: Christoph Lameter <cl@linux.com>
Cc: David Rientjes <rientjes@google.com>,
Minchan Kim <minchan.kim@gmail.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, andi@firstfloor.org
Subject: Re: [patch] mm: fix deferred congestion timeout if preferred zone is not allowed
Date: Wed, 19 Jan 2011 21:06:25 +0100 [thread overview]
Message-ID: <20110119200625.GD15568@one.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1101191351010.20403@router.home>
On Wed, Jan 19, 2011 at 01:59:01PM -0600, Christoph Lameter wrote:
> On Tue, 18 Jan 2011, David Rientjes wrote:
>
> > It depends on the semantics of NUMA_MISS: if no local nodes are allowed by
> > current's cpuset (a pretty poor cpuset config :), then it seems logical
> > that all allocations would be a miss.
>
> NUMA_MISS is defined as an allocations that did not succeed on the node
> the allocation was "intended" for. So far "intended" as been interpreted
> as allocations that are either intended for the closest numa node or the
> preferred node. One could say that the cpuset config is an "intention".
>
> Andi?
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.
-Andi
--
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-19 20:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 5:09 [patch] mm: fix deferred congestion timeout if preferred zone is not allowed 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 [this message]
2011-01-19 20:18 ` David Rientjes
2011-01-19 23:07 ` Christoph Lameter
2011-01-20 0:59 ` Minchan Kim
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=20110119200625.GD15568@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.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=minchan.kim@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).