From: David Miller <davem@davemloft.net>
To: john.fastabend@gmail.com
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
jhs@mojatatu.com, eric.dumazet@gmail.com
Subject: Re: [net-next PATCH v1 0/3] net sched rcu updates
Date: Mon, 06 Oct 2014 18:03:01 -0400 (EDT) [thread overview]
Message-ID: <20141006.180301.251258497544909892.davem@davemloft.net> (raw)
In-Reply-To: <20141006042335.6010.27000.stgit@nitbit.x32>
From: John Fastabend <john.fastabend@gmail.com>
Date: Sun, 05 Oct 2014 21:27:25 -0700
> This fixes the use of tcf_proto from RCU callbacks it requires
> moving the unbind calls out of the callbacks and removing the
> tcf_proto argument from the tcf_em_tree_destroy().
>
> This is a rework of two previous series and addresses comments
> from Cong. And should apply against latest net-next.
>
> The previous series links below for reference:
>
> (1/2) net: sched: do not use tcf_proto 'tp' argument from call_rcu
> http://patchwork.ozlabs.org/patch/396149/
>
> (2/2) net: sched: replace ematch calls to use struct net
> http://patchwork.ozlabs.org/patch/396150/
>
>
> net: sched: cls_cgroup tear down exts and ematch from rcu callback
> http://patchwork.ozlabs.org/patch/396307/
Series applied, thanks.
prev parent reply other threads:[~2014-10-06 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 4:27 [net-next PATCH v1 0/3] net sched rcu updates John Fastabend
2014-10-06 4:27 ` [net-next PATCH v1 1/3] net: sched: remove tcf_proto from ematch calls John Fastabend
2014-10-06 16:52 ` Cong Wang
2014-10-06 4:28 ` [net-next PATCH v1 2/3] net: sched: cls_cgroup tear down exts and ematch from rcu callback John Fastabend
2014-10-06 17:01 ` Cong Wang
2014-10-06 4:28 ` [net-next PATCH v1 3/3] net: sched: do not use tcf_proto 'tp' argument from call_rcu John Fastabend
2014-10-06 17:05 ` Cong Wang
2014-10-06 22:03 ` David Miller [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=20141006.180301.251258497544909892.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--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 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).