From: Rao Shoaib <rao.shoaib@oracle.com>
To: Christopher Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
joe@perches.com, willy@infradead.org, brouer@redhat.com,
linux-mm@kvack.org
Subject: Re: [PATCH 2/2] kfree_rcu() should use kfree_bulk() interface
Date: Wed, 4 Apr 2018 00:28:53 -0700 [thread overview]
Message-ID: <d6a58a0d-be8b-44e9-29c7-ef2588afefbf@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1804021217070.24404@nuc-kabylake>
On 04/02/2018 10:20 AM, Christopher Lameter wrote:
> On Sun, 1 Apr 2018, rao.shoaib@oracle.com wrote:
>
>> kfree_rcu() should use the new kfree_bulk() interface for freeing
>> rcu structures as it is more efficient.
> It would be even better if this approach could also use
>
> kmem_cache_free_bulk()
>
> or
>
> kfree_bulk()
Sorry I do not understand your comment. The patch is using kfree_bulk()
which is an inline function.
Shoaib
next prev parent reply other threads:[~2018-04-04 7:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 5:31 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-02 5:31 ` [PATCH 1/2] Move kfree_call_rcu() to slab_common.c rao.shoaib
2018-04-02 7:59 ` kbuild test robot
2018-04-02 9:45 ` kbuild test robot
2018-04-02 15:43 ` Paul E. McKenney
2018-04-02 5:31 ` [PATCH 2/2] kfree_rcu() should use kfree_bulk() interface rao.shoaib
2018-04-02 7:13 ` kbuild test robot
2018-04-02 17:20 ` Christopher Lameter
2018-04-04 7:28 ` Rao Shoaib [this message]
2018-04-03 17:22 [PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk rao.shoaib
2018-04-03 17:22 ` [PATCH 2/2] kfree_rcu() should use kfree_bulk() interface rao.shoaib
2018-04-03 20:58 ` Matthew Wilcox
2018-04-04 0:55 ` Rao Shoaib
2018-04-04 2:23 ` Matthew Wilcox
2018-04-04 7:16 ` Rao Shoaib
2018-04-04 8:39 ` Rao Shoaib
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=d6a58a0d-be8b-44e9-29c7-ef2588afefbf@oracle.com \
--to=rao.shoaib@oracle.com \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®