From: Daniel Borkmann <daniel@iogearbox.net>
To: paulmck@linux.vnet.ibm.com
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
David Miller <davem@davemloft.net>,
John Fastabend <john.fastabend@gmail.com>,
Roi Dayan <roid@mellanox.com>,
ast@fb.com, Hannes Frederic Sowa <hannes@stressinduktion.org>,
Jiri Pirko <jiri@mellanox.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net] net, sched: respect rcu grace period on cls destruction
Date: Mon, 28 Nov 2016 11:51:12 +0100 [thread overview]
Message-ID: <583C0C20.3020703@iogearbox.net> (raw)
In-Reply-To: <20161128104736.GX31360@linux.vnet.ibm.com>
On 11/28/2016 11:47 AM, Paul E. McKenney wrote:
> On Mon, Nov 28, 2016 at 10:09:16AM +0100, Daniel Borkmann wrote:
>> On 11/28/2016 07:57 AM, Cong Wang wrote:
[...]
>>> The ugly part is the work struct, I am not an RCU expert so don't know if we
>>> have any API to execute an RCU callback in process context. Paul?
>>
>> Same way we do this in BPF with prog destruction, by the way. I'm not aware
>> of any callback API for RCU that lets you do this, but maybe Paul knows.
>
> RCU callbacks are always executed in softirq context, so yes, you do need
> to use something like a work struct. (Or a wakeup to a kthread or
> whatever.)
Ok, thanks for the confirmation!
Daniel
next prev parent reply other threads:[~2016-11-28 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:18 [PATCH net] net, sched: respect rcu grace period on cls destruction Daniel Borkmann
2016-11-28 2:55 ` John Fastabend
2016-11-28 6:57 ` Cong Wang
2016-11-28 9:09 ` Daniel Borkmann
2016-11-28 10:47 ` Paul E. McKenney
2016-11-28 10:51 ` Daniel Borkmann [this message]
2016-11-29 6:55 ` Cong Wang
2016-11-29 5:16 ` Roi Dayan
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=583C0C20.3020703@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jiri@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=roid@mellanox.com \
--cc=xiyou.wangcong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.