From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <419EA96E.9030206@yahoo.com.au> Date: Sat, 20 Nov 2004 13:18:22 +1100 From: Nick Piggin MIME-Version: 1.0 Subject: Re: page fault scalability patch V11 [0/7]: overview References: <419D581F.2080302@yahoo.com.au> <419D5E09.20805@yahoo.com.au> <1100848068.25520.49.camel@gaston> <20041120020401.GC2714@holomorphy.com> In-Reply-To: <20041120020401.GC2714@holomorphy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: William Lee Irwin III Cc: Christoph Lameter , torvalds@osdl.org, akpm@osdl.org, Benjamin Herrenschmidt , Hugh Dickins , linux-mm@kvack.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org List-ID: William Lee Irwin III wrote: > On Fri, Nov 19, 2004 at 11:42:39AM -0800, Christoph Lameter wrote: > >>A. make_rss_atomic. The earlier releases contained that patch but >>then another variable (such as anon_rss) was introduced that would >> have required additional atomic operations. Atomic rss operations >> are also causing slowdowns on machines with a high number of cpus >> due to memory contention. >>B. remove_rss. Replace rss with a periodic scan over the vm to >> determine rss and additional numbers. This was also discussed on >> linux-mm and linux-ia64. The scans while displaying /proc data >> were undesirable. > > > Split counters easily resolve the issues with both these approaches > (and apparently your co-workers are suggesting it too, and have > performance results backing it). > Split counters still require atomic operations though. This is what Christoph's latest effort is directed at removing. And they'll still bounce cachelines around. (I assume we've reached the conclusion that per-cpu split counters per-mm won't fly?). -- 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: aart@kvack.org