From: Rao Shoaib <rao.shoaib@oracle.com>
To: paulmck@linux.vnet.ibm.com
Cc: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, brouer@redhat.com,
linux-mm@kvack.org
Subject: Re: [PATCH] Move kfree_call_rcu() to slab_common.c
Date: Thu, 21 Dec 2017 19:17:35 -0800 [thread overview]
Message-ID: <106f9cdb-bb0b-539d-547e-18c509ca1163@oracle.com> (raw)
In-Reply-To: <20171222013937.GA7829@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
On 12/21/2017 05:39 PM, Paul E. McKenney wrote:
>> I left it out on purpose because the call in tiny is a little different
>>
>> rcutiny.h:
>>
>> static inline void kfree_call_rcu(struct rcu_head *head,
>> A A A A A A A A A A A A A void (*func)(struct rcu_head *rcu))
>> {
>> A A A call_rcu(head, func);
>> }
>>
>> tree.c:
>>
>> void kfree_call_rcu(struct rcu_head *head,
>> A A A A A A A A A void (*func)(struct rcu_head *rcu))
>> {
>> A A A __call_rcu(head, func, rcu_state_p, -1, 1);
>> }
>> EXPORT_SYMBOL_GPL(kfree_call_rcu);
>>
>> If we want the code to be exactly same I can create a lazy version
>> for tiny as well. However,A I don not know where to move
>> kfree_call_rcu() from it's current home in rcutiny.h though. Any
>> thoughts ?
> I might be missing something subtle here, but in case I am not, my
> suggestion is to simply rename rcutiny.h's kfree_call_rcu() and otherwise
> leave it as is. If you want to update the type of the second argument,
> which got missed back in the day, there is always this:
>
> static inline void call_rcu_lazy(struct rcu_head *head, rcu_callback_t func)
> {
> call_rcu(head, func);
> }
>
> The reason that Tiny RCU doesn't handle laziness specially is because
> Tree RCU's handling of laziness is a big no-op on the single CPU systems
> on which Tiny RCU runs. So Tiny RCU need do nothing special to support
> laziness.
>
> Thanx, Paul
>
Hi Paul,
I can not just change the name as __kfree_call_rcu macro calls
kfree_call_rcu(). I have made tiny version of kfree_call_rcu() call
rcu_call_lazy() which calls call_rcu(). As far as the type is concerned,
my bad, I cut and posted from an older release. Latest code is already
using the typedef.
Shoaib
[-- Attachment #2: Type: text/html, Size: 2157 bytes --]
next prev parent reply other threads:[~2017-12-22 3:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 8:19 rao.shoaib
2017-12-21 12:36 ` Matthew Wilcox
2017-12-21 17:31 ` Rao Shoaib
2017-12-22 1:39 ` Paul E. McKenney
2017-12-22 3:17 ` Rao Shoaib [this message]
2018-01-02 20:24 ` Paul E. McKenney
2017-12-21 15:54 ` Paul E. McKenney
2017-12-21 17:06 ` Matthew Wilcox
2017-12-22 1:27 ` Paul E. McKenney
2017-12-22 1:30 ` 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=106f9cdb-bb0b-539d-547e-18c509ca1163@oracle.com \
--to=rao.shoaib@oracle.com \
--cc=brouer@redhat.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