All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Weird HTB behaviour in 2.6.17
Date: Sat, 29 Jul 2006 01:07:50 +0000	[thread overview]
Message-ID: <44CAB4E6.90307@trash.net> (raw)
In-Reply-To: <30dd942a0607271045o73dfc680r6bd2695e257a982b@mail.gmail.com>

Andy Furniss wrote:
> Marlon Dutra wrote:
> 
>> lended: 150 borrowed: 5077 giants: 3986
>> tokens: -14728330 ctokens: -21365
>>
>>> Regardless 11678670/2711 > 1500 so specify your mtu next to every rate
>>> and ceil.
>>
>> I created the class with "mtu 1500" and the result is above, same
>> behaviour. Afaik, the default mtu is 1600.
>>
>> By the way, my ethernet MTU is 1500.
>>
>> How can I prevent those giants?
> 
> 
> It seems there is a problem with some nics not obeying mtu then (I mean
> ifconfig/ip mtu) maybe it's to do with tso or something.


Right, the "problem" is related to TCP segmentation offloading (or
GSO in current kernels). The card gets large chunks of data and is
responsible for creating MTU-sized packets, which essentially means
qdiscs get to see those large chunks of data. You can disable TSO
using ethtool (but it will cost you performance) or configure your
qdisc appropriately.


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-07-29  1:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 17:45 [LARTC] Weird HTB behaviour in 2.6.17 Marlon Dutra
2006-07-28  1:21 ` Jake Altchill
2006-07-28 17:25 ` Marlon Dutra
2006-07-28 18:53 ` Andy Furniss
2006-07-28 19:12 ` Marlon Dutra
2006-07-28 19:43 ` Andy Furniss
2006-07-29  0:50 ` Jake Altchill
2006-07-29  1:07 ` Patrick McHardy [this message]
2006-07-31 16:53 ` Marlon Dutra

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=44CAB4E6.90307@trash.net \
    --to=kaber@trash.net \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.