rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	Joel Fernandes <joel@joelfernandes.org>
Cc: RCU <rcu@vger.kernel.org>, Uladzislau Rezki <urezki@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
Subject: [v2 PATCH 0/2] enhance kfree_rcu() throughput
Date: Mon, 20 Jan 2020 15:42:24 +0100	[thread overview]
Message-ID: <20200120144226.27538-1-urezki@gmail.com> (raw)

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(-)

-- 
2.20.1


             reply	other threads:[~2020-01-20 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 14:42 Uladzislau Rezki (Sony) [this message]
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 ` [v2 PATCH 0/2] enhance kfree_rcu() throughput Paul E. McKenney

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=20200120144226.27538-1-urezki@gmail.com \
    --to=urezki@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksiy.avramchenko@sonymobile.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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).