From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Christoph Lameter <cl@linux.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Mel Gorman <mel@csn.ul.ie>, Rob Mueller <robm@fastmail.fm>,
linux-kernel@vger.kernel.org, Bron Gondwana <brong@fastmail.fm>,
linux-mm <linux-mm@kvack.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [resend][PATCH] mm: increase RECLAIM_DISTANCE to 30
Date: Fri, 8 Oct 2010 22:29:30 +0530 [thread overview]
Message-ID: <20101008165930.GH5327@balbir.in.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010081044530.30029@router.home>
* Christoph Lameter <cl@linux.com> [2010-10-08 10:45:16]:
> On Fri, 8 Oct 2010, Balbir Singh wrote:
>
> > I am not sure if this makes sense, since RECLAIM_DISTANCE is supposed
> > to be a hardware parameter. Could you please help clarify what the
> > access latency of a node with RECLAIM_DISTANCE 20 to that of a node
> > with RECLAIM_DISTANCE 30 is? Has the hardware definition of reclaim
> > distance changed?
>
> 10 is the local distance. So 30 should be 3x the latency that a local
> access takes.
>
Does this patch then imply that we should do zone_reclaim only for 3x
nodes and not 2x nodes as we did earlier.
> > I suspect the side effect is the zone_reclaim_mode is not set to 1 on
> > bootup for the 2-4 socket machines you mention, which results in
> > better VM behaviour?
>
> Right.
>
--
Three Cheers,
Balbir
--
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:[~2010-10-08 16:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 1:48 KOSAKI Motohiro
2010-10-08 9:04 ` Balbir Singh
2010-10-08 15:45 ` Christoph Lameter
2010-10-08 16:59 ` Balbir Singh [this message]
2010-10-08 17:56 ` Christoph Lameter
2010-10-12 2:11 ` David Rientjes
2010-10-12 2:17 ` KOSAKI Motohiro
2010-10-12 3:12 ` David Rientjes
2010-10-12 4:07 ` KOSAKI Motohiro
2010-10-12 6:41 ` Balbir Singh
2010-10-12 1:55 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2010-10-25 3:24 KOSAKI Motohiro
2010-10-25 4:35 ` KAMEZAWA Hiroyuki
2010-10-08 1:48 KOSAKI Motohiro
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=20101008165930.GH5327@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=brong@fastmail.fm \
--cc=cl@linux.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=rientjes@google.com \
--cc=robm@fastmail.fm \
/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