Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	 cake@lists.bufferbloat.net
Subject: Re: [Cake] Possible BUG - parent backlog incorrectly updated in case of NET_XMIT_CN
Date: Sun, 12 Jun 2016 09:31:25 -0700	[thread overview]
Message-ID: <1465749085.7945.81.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <98AFD8C3-2343-4B8B-BFB0-6F877161A039@gmail.com>

On Sat, 2016-06-11 at 19:41 +0300, Jonathan Morton wrote:
> > On 11 Jun, 2016, at 12:11, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> > 
> > And now there's a version 2 of Eric's fix: http://marc.info/?l=linux-netdev&m=146507012302643&w=2
> > 
> > Does this change apply to cake?
> 
> I suppose this answers the question of which packet’s size should be
> used in the correction factor.  Of course, by this time in the enqueue
> process, the original packet length has been replaced by the
> overhead-corrected one in Cake, though I can save a copy for this
> purpose.
> 
> And there’s also the problem that we might not need to drop packets as
> large as the incoming packet in order to fit the latter into the queue
> - so this corrected correction may be *negative* (the queue is longer
> than before) - but qdisc_tree_reduce_backlog() only takes an unsigned
> parameter here.

That's a very minor detail.

If the code does :

reduce_backlog(unsigned quantity)
{
	q->backlog -= quantity;
}

Then the fact that @quantity is signed or unsigned is irrelevant.

You can submit a patch if you want ;)
> 


> IMHO the NET_XMIT_CN semantics are broken.  It might be better to drop
> support for it, since it should rarely be triggered.

What exact part is broken ?
Semantic looks good to me.

Implementations might be broken after recent Cong Wang patches.




  reply	other threads:[~2016-06-12 16:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 11:20 Kevin Darbyshire-Bryant
2016-06-07 14:50 ` Jonathan Morton
2016-06-07 15:05   ` Kevin Darbyshire-Bryant
2016-06-11  9:11     ` Kevin Darbyshire-Bryant
2016-06-11 16:41       ` Jonathan Morton
2016-06-12 16:31         ` Eric Dumazet [this message]
2016-06-12 16:40           ` Dave Taht
2016-06-12 17:48             ` Eric Dumazet
2016-06-12 17:51               ` Jonathan Morton
2016-06-12 18:19                 ` Eric Dumazet
2016-06-12 17:59           ` Jonathan Morton
2016-06-12 19:04             ` Eric Dumazet
2016-06-12 20:40               ` Benjamin Cronce

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1465749085.7945.81.camel@edumazet-glaptop3.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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