From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757271AbYHVTwi (ORCPT ); Fri, 22 Aug 2008 15:52:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752205AbYHVTwb (ORCPT ); Fri, 22 Aug 2008 15:52:31 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]:41101 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751941AbYHVTwa (ORCPT ); Fri, 22 Aug 2008 15:52:30 -0400 Date: Fri, 22 Aug 2008 12:52:26 -0700 From: "Paul E. McKenney" To: Christoph Lameter Cc: Pekka Enberg , Ingo Molnar , Jeremy Fitzhardinge , Nick Piggin , Andi Kleen , "Pallipadi, Venkatesh" , Suresh Siddha , Jens Axboe , Rusty Russell , Linux Kernel Mailing List Subject: Re: [PATCH 2/2] smp_call_function: use rwlocks on queues rather than rcu Message-ID: <20080822195226.GJ6744@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <48AE0883.6050701@goop.org> <20080822062800.GQ14110@elte.hu> <84144f020808220006n25d684b1n9db306ddc4f58c4c@mail.gmail.com> <48AEC6B2.1080701@linux-foundation.org> <20080822151156.GA6744@linux.vnet.ibm.com> <48AEF3FD.70906@linux-foundation.org> <20080822182915.GG6744@linux.vnet.ibm.com> <48AF0735.60402@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48AF0735.60402@linux-foundation.org> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 22, 2008 at 01:36:37PM -0500, Christoph Lameter wrote: > Paul E. McKenney wrote: > > >>> So on your these large boxes, read-only cachelines are preferentially > >>> ejected from the cache, so that one should write to per-CPU data > >>> occasionally to keep it resident? Or is the issue the long RCU grace > >>> periods which allow the structure being freed to age out of all relevant > >>> caches? (My guess would be the second.) > >> The issue are the RCU grace period that are generally long enough to make the > >> cacheline fall out of all caches. > > > > Would it make sense to push the freed-by-RCU memory further up the > > hierarchy, so that such memory is not mistaken for recently freed > > hot-in-cache memory? > > That would mean passing a gfp flag like __GFP_COLD on free from RCU? Or how > would that work at the higher levels? I was indeed thinking in terms of the free from RCU being specially marked. Thanx, Paul