From: Andi Kleen <ak@suse.de>
To: Paul Jackson <pj@sgi.com>
Cc: dada1@cosmosbay.com, clameter@engr.sgi.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au,
Simon.Derr@bull.net, ak@suse.de
Subject: Re: [PATCH] Cpuset: rcu optimization of page alloc hook
Date: Wed, 14 Dec 2005 05:02:36 +0100 [thread overview]
Message-ID: <20051214040236.GF23384@wotan.suse.de> (raw)
In-Reply-To: <20051213195457.4e2b31af.pj@sgi.com>
> But, boy oh boy, that synchronize_rcu() call sure takes it time.
>
> My cpuset torture test was creating, destroying and abusing about 2600
> cpusets/sec before this change, and now it does about 144 cpusets/sec.
>
> That cost 95% of the performance. This only hits on the cost of
> attaching a task to a different cpuset (by writing its <pid> to
> some other cpuset 'tasks' file.)
That is why call_rcu.et.al. is a better interface if you want performance.
It runs the freeing batched in the background.
-Andi
next prev parent reply other threads:[~2005-12-14 4:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 23:31 [PATCH] Cpuset: rcu optimization of page alloc hook Paul Jackson
2005-12-12 3:29 ` Andi Kleen
2005-12-12 6:11 ` Paul Jackson
2005-12-12 6:21 ` Andi Kleen
2005-12-12 6:50 ` Paul Jackson
2005-12-12 8:49 ` Eric Dumazet
2005-12-12 8:54 ` Nick Piggin
2005-12-12 9:06 ` Eric Dumazet
2005-12-12 9:11 ` Andrew Morton
2005-12-12 9:38 ` Nick Piggin
2005-12-12 10:02 ` Paul Jackson
2005-12-12 10:12 ` Andrew Morton
2005-12-13 15:53 ` Paul Jackson
2005-12-13 16:31 ` Eric Dumazet
2005-12-13 17:42 ` Christoph Lameter
2005-12-13 17:56 ` Eric Dumazet
2005-12-13 18:07 ` Christoph Lameter
2005-12-13 21:03 ` Paul Jackson
2005-12-13 21:16 ` Christoph Lameter
2005-12-13 21:38 ` Eric Dumazet
2005-12-13 22:23 ` Paul Jackson
2005-12-13 22:29 ` Christoph Lameter
2005-12-14 3:54 ` Paul Jackson
2005-12-14 4:02 ` Andi Kleen [this message]
2005-12-14 4:06 ` Paul Jackson
2005-12-14 8:06 ` Eric Dumazet
2005-12-14 8:40 ` Paul Jackson
2005-12-13 20:08 ` Paul Jackson
2005-12-13 20:29 ` Eric Dumazet
2005-12-13 22:35 ` Paul Jackson
2005-12-13 21:44 ` Paul Jackson
2005-12-13 17:37 ` Christoph Lameter
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=20051214040236.GF23384@wotan.suse.de \
--to=ak@suse.de \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox