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: Sun, 17 Oct 2010 22:36:18 +0200	[thread overview]
Message-ID: <20101017203618.GA1889@del.dom.local> (raw)
In-Reply-To: <20101016212434.72ae5250.billfink@mindspring.com>

On Sat, Oct 16, 2010 at 09:24:34PM -0400, Bill Fink wrote:
> On Sat, 16 Oct 2010, Jarek Poplawski wrote:
...
> > http://code.google.com/p/pspacer/wiki/HTBon10GbE
> >  
> > If it doesn't help reconsider hfsc.
> 
> Thanks for the link.  From his results, it appears you can
> get better accuracy by keeping TSO/GSO enabled and upping
> the tc mtu parameter to 64000.  I will have to try that out.

Sure, but you have to remember that scheduler doesn't know real packet
sizes and rate tables are less accurate especially for smaller packets,
so it depends on conditions.

> For the very high bandwidth cases I tend to deal with, would
> there be any advantage to further reducing the PSCHED_SHIFT
> from its current value of 6?

If you don't use low rates and/or large buffers it might be a good
idea, especially on x64 (for 32-bit longs htb needs some change for
this value below 5).

Jarek P.

  reply	other threads:[~2010-10-17 20:36 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
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 [this message]
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=20101017203618.GA1889@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).