All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC and default qdisc backlog
Date: Thu, 23 Mar 2006 04:03:57 +0000	[thread overview]
Message-ID: <44221E2D.50902@trash.net> (raw)
In-Reply-To: <033e01c64d41$fd1ae8d0$1414a8c0@provsol.int>

Jason Boxman wrote:
> On Wednesday 22 March 2006 19:13, James Nelson wrote:
> 
>>Thanks for all of your help Patrick!
>>
>>Just so I'm clear.  If hfsc at the class level shows no overlimits and no
>>packet dropps, then hfsc is not effecting my traffic any different (from a
>>throughput perspective computational computer slowness aside) then if i had
>>no traffic shapping in place?
> 
> 
> Well, surely if you're not delaying or dropping any traffic on your side of 
> the pipe, you're either using less bandwidth than you have or you've 
> overstated the true size of your upstream link.  In either case, no shaping 
> can occur as ordering packets has little effect if there's no bottleneck.

Not exactly. Overlimit means no eligible class could be found because
_all_ classes are over their limits, it can't be accounted to a specific
class but only globally. There is no way (except for backlog
statistics, but backlogs can also happen because of other reasons)
to tell if a single class is affected by rate limiting or not.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-03-23  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 23:48 [LARTC] HFSC and default qdisc backlog James Nelson
2006-03-22  0:03 ` Patrick McHardy
2006-03-23  0:13 ` James Nelson
2006-03-23  0:27 ` Jason Boxman
2006-03-23  4:03 ` Patrick McHardy [this message]
2006-04-12 15:04 ` Andy Furniss

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=44221E2D.50902@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.