netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Bill Fink <billfink@mindspring.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Rick Jones <rick.jones2@hp.com>,
	Steven Brudenell <steven.brudenell@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: tbf/htb qdisc limitations
Date: Sat, 16 Oct 2010 00:05:35 +0200	[thread overview]
Message-ID: <20101015220535.GA1997@del.dom.local> (raw)
In-Reply-To: <20101015173746.12c7c40a.billfink@mindspring.com>

On Fri, Oct 15, 2010 at 05:37:46PM -0400, Bill Fink wrote:
...
> i7test7% tc -s -d qdisc show dev eth2
> qdisc prio 1: root refcnt 33 bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
>  Sent 11028687119 bytes 1223828 pkt (dropped 293, overlimits 0 requeues 0) 
>  backlog 0b 0p requeues 0 
> qdisc tbf 10: parent 1:1 rate 8900Mbit burst 1112500b/64 mpu 0b lat 4295.0s 
>  Sent 11028687077 bytes 1223827 pkt (dropped 293, overlimits 593 requeues 0) 
>  backlog 0b 0p requeues 0 
> 
> I'm not sure how you can have so many dropped but not have
> any TCP retransmissions (or not show up as requeues).  But
> there's probably something basic I just don't understand
> about how all this stuff works.

Me either, but it seems higher "limit" might help with these drops.

Jarek P.

  reply	other threads:[~2010-10-15 22:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 20:58 tbf/htb qdisc limitations Steven Brudenell
2010-10-10 11:23 ` Jarek Poplawski
2010-10-11 22:27   ` Steven Brudenell
2010-10-12 10:10     ` Jarek Poplawski
2010-10-12 19:31       ` Steven Brudenell
2010-10-12 21:59         ` Jarek Poplawski
2010-10-12 22:17           ` Rick Jones
2010-10-13  6:26             ` Jarek Poplawski
2010-10-14  3:36               ` Bill Fink
2010-10-14  4:01                 ` Eric Dumazet
2010-10-14  6:34                   ` Bill Fink
2010-10-14  6:44                 ` Jarek Poplawski
2010-10-14  7:13                   ` Bill Fink
2010-10-14  8:09                     ` Jarek Poplawski
2010-10-14  8:50                       ` Jarek Poplawski
2010-10-15  6:37                         ` Bill Fink
2010-10-15  6:44                           ` Eric Dumazet
2010-10-15 21:37                             ` Bill Fink
2010-10-15 22:05                               ` Jarek Poplawski [this message]
2010-10-16  4:51                                 ` Bill Fink
2010-10-16 20:58                                   ` Jarek Poplawski
2010-10-17  1:24                                     ` Bill Fink
2010-10-17 20:36                                       ` Jarek Poplawski
2010-10-19  7:37                                         ` Bill Fink
2010-10-20 11:06                                           ` Jarek Poplawski
2010-10-27  4:51                                             ` Bill Fink
2010-10-27  9:48                                               ` Jarek Poplawski
2010-10-15  8:18                           ` Jarek Poplawski

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=20101015220535.GA1997@del.dom.local \
    --to=jarkao2@gmail.com \
    --cc=billfink@mindspring.com \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    --cc=steven.brudenell@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).