From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
RCU <rcu@vger.kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
Subject: Re: [v2 PATCH 0/2] enhance kfree_rcu() throughput
Date: Tue, 21 Jan 2020 17:16:18 -0800 [thread overview]
Message-ID: <20200122011618.GB2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200120144226.27538-1-urezki@gmail.com>
On Mon, Jan 20, 2020 at 03:42:24PM +0100, Uladzislau Rezki (Sony) wrote:
> Here we go with V2 version of the "support kfree_bulk() interface in
> kfree_rcu()" patchest. Apart of that there is one more, it just adds
> a trace event for kfree_bulk() call.
>
> Boths patches are based on "dev.2020.01.10a" branch of the linux-rcu.git
>
> V1 -> V2:
> - fix and support debugobjects;
> - updated the commit message of [1]. Added test results
> of CONFIG_SLAB / CONFIG_SLUB configurations together
> with recent new parameter kfree_vary_obj_size=1;
> - add more comments.
>
> Rezki (Sony) (2):
> [1] rcu/tree: support kfree_bulk() interface in kfree_rcu()
> [2] rcu/tree: add a trace invoke event of the kfree_bulk()
>
> include/trace/events/rcu.h | 28 +++++
> kernel/rcu/tree.c | 207 ++++++++++++++++++++++++++++++-------
> 2 files changed, 200 insertions(+), 35 deletions(-)
Both queued for further review and testing, thank you!
Thanx, Paul
prev parent reply other threads:[~2020-01-22 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:42 [v2 PATCH 0/2] enhance kfree_rcu() throughput Uladzislau Rezki (Sony)
2020-01-20 14:42 ` [v2 PATCH 1/2] rcu/tree: support kfree_bulk() interface in kfree_rcu() Uladzislau Rezki (Sony)
2020-01-20 14:42 ` [v2 PATCH 2/2] rcu/tree: add a trace invoke event of the kfree_bulk() Uladzislau Rezki (Sony)
2020-01-22 1:16 ` Paul E. McKenney [this message]
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=20200122011618.GB2935@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.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;
as well as URLs for NNTP newsgroup(s).