Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: edumazet@google.com, netdev@vger.kernel.org,
	kuznet@ms2.inr.ac.ru, jhs@mojatatu.com
Subject: Re: inaccurate packet scheduling
Date: Thu, 07 Feb 2013 09:47:38 -0800	[thread overview]
Message-ID: <1360259258.28557.57.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130207173909.GA1651@minipsycho.orion>

On Thu, 2013-02-07 at 18:39 +0100, Jiri Pirko wrote:
> Thu, Feb 07, 2013 at 05:39:35PM CET, eric.dumazet@gmail.com wrote:
> >On Thu, 2013-02-07 at 17:13 +0100, Jiri Pirko wrote:
> >
> >> >I tried kernel with this patch in. I also ported
> >> >56b765b79e9a78dc7d3f8850ba5e5567205a3ecd to tbf. I'm getting always the
> >> >similar numbers with iperf. There must be something else needed :/
> >> 
> >> Any other ideas?
> >
> >You didn't post any patch, how can I comment on them ?
> 
> Okay, sorry, here it is. But as I said, it did not help.
> 
> Subject: [patch net-next RFC] tbf: improved accuracy at high rates
> 
> Current TBF uses rate table computed by the "tc" userspace program,
> which has the following issue:
> 
> The rate table has 256 entries to map packet lengths to
> token (time units).  With TSO sized packets, the 256 entry granularity
> leads to loss/gain of rate, making the token bucket inaccurate.
> 
> Thus, instead of relying on rate table, this patch explicitly computes
> the time and accounts for packet transmission times with nanosecond
> granularity.
> 
> This is a followup to 56b765b79e9a78dc7d3f8850ba5e5567205a3ecd
> 
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
> ---

This patch doesnt change  q->max_size

So you hit this :

if (qdisc_pkt_len(skb) > q->max_size)
    return qdisc_reshape_fail(skb, sch);

I thought this point was already mentioned in my previous mails.

  reply	other threads:[~2013-02-07 17:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 15:04 inaccurate packet scheduling Jiri Pirko
2012-12-18 16:26 ` Stephen Hemminger
2012-12-18 16:51   ` Eric Dumazet
2013-01-02 15:26     ` Jiri Pirko
2013-01-02 16:34       ` Eric Dumazet
2013-01-08 13:30         ` Jiri Pirko
2013-01-24  8:05           ` Jiri Pirko
2013-01-24 14:01             ` Eric Dumazet
2013-01-29 12:23               ` Jiri Pirko
2013-01-29 16:13                 ` Eric Dumazet
2013-01-30 12:14                   ` Jiri Pirko
2013-02-07 16:13                     ` Jiri Pirko
2013-02-07 16:39                       ` Eric Dumazet
2013-02-07 17:39                         ` Jiri Pirko
2013-02-07 17:47                           ` Eric Dumazet [this message]
2013-02-07 18:56                             ` Jiri Pirko
2012-12-18 17:54   ` Jiri Pirko
2012-12-18 18:06     ` Eric Dumazet
2012-12-18 18:40       ` Jiri Pirko
2012-12-18 18:43         ` Stephen Hemminger

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=1360259258.28557.57.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuznet@ms2.inr.ac.ru \
    --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