netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [Patch net-next v2 2/4] net_sched: update hierarchical backlog too
Date: Mon, 02 Nov 2015 13:20:57 -0800	[thread overview]
Message-ID: <1446499257.23275.33.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAHA+R7NkU3Bme5MbgFraOo=7SRYUF+F-6owyzFxfVidjc2AxMw@mail.gmail.com>

On Mon, 2015-11-02 at 13:09 -0800, Cong Wang wrote:
> (Sorry for the delay)
> 
> On Fri, Oct 30, 2015 at 12:30 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > On Fri, 2015-10-30 at 11:22 -0700, Cong Wang wrote:
> >> diff --git a/net/sched/sch_sfq.c b/net/sched/sch_sfq.c
> >> index 3abab53..498f0a2 100644
> >> --- a/net/sched/sch_sfq.c
> >> +++ b/net/sched/sch_sfq.c
> >> @@ -346,7 +346,7 @@ static int
> >>  sfq_enqueue(struct sk_buff *skb, struct Qdisc *sch)
> >>  {
> >>       struct sfq_sched_data *q = qdisc_priv(sch);
> >> -     unsigned int hash;
> >> +     unsigned int hash, dropped;
> >>       sfq_index x, qlen;
> >>       struct sfq_slot *slot;
> >>       int uninitialized_var(ret);
> >> @@ -461,7 +461,7 @@ sfq_enqueue(struct sk_buff *skb, struct Qdisc *sch)
> >>               return NET_XMIT_SUCCESS;
> >>
> >>       qlen = slot->qlen;
> >> -     sfq_drop(sch);
> >> +     dropped = sfq_drop(sch);
> >>       /* Return Congestion Notification only if we dropped a packet
> >>        * from this flow.
> >>        */
> >> @@ -469,7 +469,7 @@ sfq_enqueue(struct sk_buff *skb, struct Qdisc *sch)
> >>               return NET_XMIT_CN;
> >
> >
> > I believe you missed the NET_XMIT_CN cases.
> >
> > SFQ can drop a prior packet, and queue current packet.
> >
> > qdisc_tree_reduce_backlog() wont be called to update parents.
> >
> > Not sure about other qdisc(s)
> 
> Are you saying some qdisc_tree_reduce_backlog() is missing? It could be,
> since I don't audit that, if so, I'd do that in a separated patch, because this
> patch is supposed to fix existing qdisc_tree_reduce_backlog().
> 
> Does this make sense for you?

Well, before your changes, the qdisc_tree_decrease_qlen(sch, 0) would
have been useless, since qdisc_tree_decrease_qlen() does nothing in this
case [1]

But after your changes, we need to change the backlog, even if the qlen
does not change.

Maybe I missed something, but your patch is not really obvious ;)

[1]
void qdisc_tree_decrease_qlen(struct Qdisc *sch, unsigned int n)
{
        ...
        if (n == 0)
                return;

  reply	other threads:[~2015-11-02 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 18:22 [Patch net-next v2 0/4] net_sched: update backlog for hierarchical qdisc's Cong Wang
2015-10-30 18:22 ` [Patch net-next v2 1/4] net_sched: introduce qdisc_replace() helper Cong Wang
2015-10-30 18:22 ` [Patch net-next v2 2/4] net_sched: update hierarchical backlog too Cong Wang
2015-10-30 19:30   ` Eric Dumazet
2015-11-02 21:09     ` Cong Wang
2015-11-02 21:20       ` Eric Dumazet [this message]
2015-11-02 21:50         ` Cong Wang
2015-10-30 18:22 ` [Patch net-next v2 3/4] sch_htb: update backlog as well Cong Wang
2015-10-30 18:22 ` [Patch net-next v2 4/4] sch_dsmark: " Cong Wang

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=1446499257.23275.33.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=cwang@twopensource.com \
    --cc=jhs@mojatatu.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).