From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: netoptimizer@brouer.com, jesper.brouer@gmail.com,
jesper@brouer.com, aravinda@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Fw: Re: Linux Plumbers funding to go? / two minconf's
Date: Mon, 10 Aug 2015 09:45:12 -0700 [thread overview]
Message-ID: <20150810164512.GD3862@linux.vnet.ibm.com> (raw)
On Thu, Aug 06, 2015 at 05:39:28PM +0200, Jesper Dangaard Brouer wrote:
> Specifically for Paul: I would like to discuss with you Paul how we can
> speed up RCU object freeing, by using my new SLAB/slub bulk API[*].
> The delayed free by RCU cause us to hit the slub slowpath... I'm hoping
> to speedup this up by bulk freeing... hoping to mitigate the effect of
> "rcuo" slowdown. Specifically I'm looking for stress testing RCU
> tools, as I want to measure the effect/improvement.
>
> [*] http://thread.gmane.org/gmane.linux.kernel.mm/135704
>
> p.s. I'm on vacation ATM, thus Cc. jesper.brouer@gmail.com or
> jesper@brouer.com.
Just thought I should get you in touch with Aravida Prasad (CCed), who
has been doing some related work in speeding up RCU/slab freeing.
Thanx, Paul
reply other threads:[~2015-08-10 16:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150810164512.GD3862@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=aravinda@linux.vnet.ibm.com \
--cc=jesper.brouer@gmail.com \
--cc=jesper@brouer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netoptimizer@brouer.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
Powered by JetHome