From: Chris Mason <mason@suse.de>
To: Dimitri Sivanich <sivanich@sgi.com>
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
Date: Wed, 22 Feb 2006 18:56:05 -0500 [thread overview]
Message-ID: <200602221856.07262.mason@suse.de> (raw)
In-Reply-To: <20060222220037.GC3734@sgi.com>
On Wednesday 22 February 2006 17:00, Dimitri Sivanich wrote:
> 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.
Right, but I'm suggesting that we might want to fix kmem_cache_free as well.
I think your patch has value even with kmem_cache_free fixed. Given that the
high cost parts of kmem_cache_free seem to be numa specific, fixing it seems
like a good idea in general.
-chris
next prev parent reply other threads:[~2006-02-22 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 14:51 [PATCH] Enable remote RCU callback processing on SMP systems Dimitri Sivanich
2006-02-22 20:23 ` Chris Mason
2006-02-22 22:00 ` Dimitri Sivanich
2006-02-22 23:56 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 20:38 Dimitri Sivanich
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=200602221856.07262.mason@suse.de \
--to=mason@suse.de \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=okir@suse.de \
--cc=paulmck@us.ibm.com \
--cc=sivanich@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.