Netdev List
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, mlxsw@mellanox.com,
	edumazet@google.com, daniel@iogearbox.net,
	alexander.h.duyck@intel.com, willemb@google.com,
	john.fastabend@gmail.com
Subject: Re: [patch net-next v2] net: core: introduce mini_Qdisc and eliminate usage of tp->q for clsact fastpath
Date: Thu, 26 Oct 2017 08:54:56 -0700	[thread overview]
Message-ID: <20171026155454.nkh5ykb2bw35wpnb@ast-mbp> (raw)
In-Reply-To: <20171026094103.10164-1-jiri@resnulli.us>

On Thu, Oct 26, 2017 at 11:41:03AM +0200, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@mellanox.com>
> 
> In sch_handle_egress and sch_handle_ingress tp->q is used only in order
> to update stats. So stats and filter list are the only things that are
> needed in clsact qdisc fastpath processing. Introduce new mini_Qdisc
> struct to hold those items. This removes need for tp->q usage without
> added overhead.

that is false claim. The patch adds run-time overhead instead.

> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
> ---
> v1->v2:
> - Use dev instead of skb->dev in sch_handle_egress as pointed out by Daniel
> - Fixed synchronize_rcu_bh() in mini_qdisc_disable and commented
...
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 24ac908..44ea1c3 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -3274,14 +3274,16 @@ EXPORT_SYMBOL(dev_loopback_xmit);
>  static struct sk_buff *
>  sch_handle_egress(struct sk_buff *skb, int *ret, struct net_device *dev)
>  {
> -	struct tcf_proto *cl = rcu_dereference_bh(dev->egress_cl_list);
> +	struct mini_Qdisc *miniq = rcu_dereference_bh(dev->miniq_egress);
>  	struct tcf_result cl_res;
> +	struct tcf_proto *cl;
>  
> -	if (!cl)
> +	if (!miniq)
>  		return skb;
> +	cl = rcu_dereference_bh(miniq->filter_list);

Just like Daniel pointed out in the earlier version of the patch
it adds another rcu dereference to critical path of execution
for every packet...

> @@ -4189,16 +4191,19 @@ sch_handle_ingress(struct sk_buff *skb, struct packet_type **pt_prev, int *ret,
>  		   struct net_device *orig_dev)
>  {
>  #ifdef CONFIG_NET_CLS_ACT
> -	struct tcf_proto *cl = rcu_dereference_bh(skb->dev->ingress_cl_list);
> +	struct mini_Qdisc *miniq = rcu_dereference_bh(skb->dev->miniq_ingress);
>  	struct tcf_result cl_res;
> +	struct tcf_proto *cl;
>  
>  	/* If there's at least one ingress present somewhere (so
>  	 * we get here via enabled static key), remaining devices
>  	 * that are not configured with an ingress qdisc will bail
>  	 * out here.
>  	 */
> -	if (!cl)
> +	if (!miniq)
>  		return skb;
> +	cl = rcu_dereference_bh(miniq->filter_list);

... both ingress and egress paths.
There gotta be very strong reasons to penalize all users for this
and I don't see them in commit log.

  reply	other threads:[~2017-10-26 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  9:41 [patch net-next v2] net: core: introduce mini_Qdisc and eliminate usage of tp->q for clsact fastpath Jiri Pirko
2017-10-26 15:54 ` Alexei Starovoitov [this message]
2017-10-26 16:22   ` Jiri Pirko
2017-10-26 17:18     ` John Fastabend
2017-10-27  7:25       ` Jiri Pirko

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=20171026155454.nkh5ykb2bw35wpnb@ast-mbp \
    --to=alexei.starovoitov@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=john.fastabend@gmail.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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