Date: Wed, 22 Feb 2006 16:00:37 -0600
From: Dimitri Sivanich <sivanich@sgi.com>
To: Chris Mason <mason@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel <linux-kernel@vger.kernel.org>,
       "Paul E. McKenney" <paulmck@us.ibm.com>,
       Dipankar Sarma <dipankar@in.ibm.com>, okir@suse.de
Subject: Re: [PATCH] Enable remote RCU callback processing on SMP systems
Message-ID: <20060222220037.GC3734@sgi.com>
References: <20060206145137.GA30059@sgi.com> <200602221523.23739.mason@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200602221523.23739.mason@suse.de>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 873
Lines: 17

On Wed, Feb 22, 2006 at 03:23:22PM -0500, Chris Mason wrote:
> Aside from the possible race we talked about in __rcu_process_callbacks, I 
> don't have huge objections here.  But if the underlying problem is the cost 
> of kmem_cache_free, would it be better to limit that instead of trying to 
> push the latency around to specific cpus?

The current problem is the cost of kmem_cache_free.  What this
patch will do (versus limiting the cost of kmem_cache_free, if
that's at all possible) is to protect the cpus configured as
such against other costly sections of code that may be lurking
or that might be added in the future.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/