netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next] cbq: remove only caller of qdisc->drop()
Date: Tue, 07 Jun 2016 17:11:30 -0700 (PDT)	[thread overview]
Message-ID: <20160607.171130.496741132362708928.davem@davemloft.net> (raw)
In-Reply-To: <1465248027-21652-1-git-send-email-fw@strlen.de>

From: Florian Westphal <fw@strlen.de>
Date: Mon,  6 Jun 2016 23:20:27 +0200

> since initial revision of cbq in 2004 iproute2 never implemented
> support for TCA_CBQ_OVL_STRATEGY, which is what needs to be set to
> activate the class->drop() call (TC_CBQ_OVL_DROP strategy must be
> set by userspace).
> 
> So lets remove this.  We can even do this in a backwards compatible
> way by switching ovl_drop to perform a dequeue+drop on the leaf.
> 
> A followup commit can then remove all .drop qdisc methods since this
> was the only caller.
> 
> Signed-off-by: Florian Westphal <fw@strlen.de>

I don't see anything, anywhere, using TCA_CBQ_OVL_STRATEGY nor the
various strategy type values.

iproute2 seems to notice the attribute in dumps, but doesn't do
anything with it other than verify that it's size meets some minimum.

It seems really safe to kill this thing off, flag an error if someone
tries to set the attribute, and therefore kill off all of the non-default
cbq_ovl_*() functions.

>   I think it would be safe to just ignore TCA_CBQ_POLICE and change the
>   qdiscs to drop right away.
> 
>   Does anyone have a reason to leave this in the tree?  Thanks!

The TCA_CBQ_POLICE situation looks similar to the TCA_CBQ_OVL_STRATEGY
one to me.

Thanks.

      parent reply	other threads:[~2016-06-08  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 21:20 [PATCH -next] cbq: remove only caller of qdisc->drop() Florian Westphal
2016-06-06 22:13 ` Eric Dumazet
2016-06-06 22:52   ` Florian Westphal
2016-06-08  0:11 ` 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=20160607.171130.496741132362708928.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).