From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756874Ab0JLCRK (ORCPT ); Mon, 11 Oct 2010 22:17:10 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:58589 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756450Ab0JLCRJ (ORCPT ); Mon, 11 Oct 2010 22:17:09 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: David Rientjes Subject: Re: [resend][PATCH] mm: increase RECLAIM_DISTANCE to 30 Cc: kosaki.motohiro@jp.fujitsu.com, Christoph Lameter , Balbir Singh , Mel Gorman , Rob Mueller , linux-kernel@vger.kernel.org, Bron Gondwana , linux-mm In-Reply-To: References: Message-Id: <20101012111451.AD2E.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Tue, 12 Oct 2010 11:17:04 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Fri, 8 Oct 2010, Christoph Lameter wrote: > > > It implies that zone reclaim is going to be automatically enabled if the > > maximum latency to the memory farthest away is 3 times or more that of a > > local memory access. > > > > It doesn't determine what the maximum latency to that memory is, it relies > on whatever was defined in the SLIT; the only semantics of that distance > comes from the ACPI spec that states those distances are relative to the > local distance of 10. Right. but do we need to consider fake SLIT case? I know actually such bogus slit are there. but I haven't seen such fake SLIT made serious trouble.