From: Pieter Jansen van Vuuren <pieter.jansenvanvuuren@netronome.com>
To: Manish Kurup <kurup.manish@gmail.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, jakub.kicinski@netronome.com,
simon.horman@netronome.com, john.hurley@netronome.com,
oss-drivers@netronome.com, netdev@vger.kernel.org,
aring@mojatatu.com, mrv@mojatatu.com,
Manish Kurup <manish.kurup@verizon.com>
Subject: Re: [PATCH net-next v6 3/3] act_vlan: VLAN action rewrite to use RCU lock/unlock and update
Date: Mon, 6 Nov 2017 18:37:31 +0000 [thread overview]
Message-ID: <20171106183731.3e1e88fc@pieter-Netronome> (raw)
In-Reply-To: <1509724247-5721-1-git-send-email-manish.kurup@verizon.com>
On Fri, 3 Nov 2017 11:50:47 -0400
Manish Kurup <kurup.manish@gmail.com> wrote:
> Using a spinlock in the VLAN action causes performance issues when the VLAN
> action is used on multiple cores. Rewrote the VLAN action to use RCU read
> locking for reads and updates instead.
>
> Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
> Acked-by: Jiri Pirko <jiri@mellanox.com>
> Signed-off-by: Manish Kurup <manish.kurup@verizon.com>
> ---
> include/net/tc_act/tc_vlan.h | 46 +++++++++++++++++++++------
> net/sched/act_vlan.c | 75
> ++++++++++++++++++++++++++++++-------------- 2 files changed, 88
> insertions(+), 33 deletions(-)
...
>
> +static void tcf_vlan_cleanup(struct tc_action *a, int bind)
> +{
> + struct tcf_vlan *v = to_vlan(a);
> + struct tcf_vlan_params *p;
> +
> + p = rcu_dereference_protected(v->vlan_p, 1);
> + kfree_rcu(p, rcu);
> +}
> +
> static int tcf_vlan_dump(struct sk_buff *skb, struct tc_action *a,
> int bind, int ref)
> {
> unsigned char *b = skb_tail_pointer(skb);
> struct tcf_vlan *v = to_vlan(a);
> + struct tcf_vlan_params *p = rtnl_dereference(v->vlan_p);
nack. This fails reverse xmas-tree.
next prev parent reply other threads:[~2017-11-06 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 15:50 [PATCH net-next v6 3/3] act_vlan: VLAN action rewrite to use RCU lock/unlock and update Manish Kurup
2017-11-06 18:37 ` Pieter Jansen van Vuuren [this message]
2017-11-07 16:54 ` Alexander Duyck
2017-11-07 17:08 ` Pieter Jansen van Vuuren
2017-11-08 0:07 ` David Miller
[not found] ` <CAJrKpLZenHyuZimWE0CfHePFktB0B-7sa-BO1ff29sXqtiN7EA@mail.gmail.com>
2017-11-08 11:43 ` Fwd: " Manish Kurup
2017-11-08 12:13 ` Manish Kurup
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=20171106183731.3e1e88fc@pieter-Netronome \
--to=pieter.jansenvanvuuren@netronome.com \
--cc=aring@mojatatu.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.hurley@netronome.com \
--cc=kurup.manish@gmail.com \
--cc=manish.kurup@verizon.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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 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).