netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: hadi@cyberus.ca, netdev@vger.kernel.org
Subject: Re: HTB/HSFC shaping precision
Date: Tue, 20 Nov 2007 21:00:56 +0100	[thread overview]
Message-ID: <47433CF8.70501@o2.pl> (raw)
In-Reply-To: <20071120092317.M96721@visp.net.lb>

Denys Fedoryshchenko wrote, On 11/20/2007 10:43 AM:
... 

> If let's say i will limit bandwidth to 1Mbps, and will try to send packets 
> will 100Mbps speed, and will check which packets will be dropped.

As a matter of fact, I wonder why you're so afraid of this dropping. It's
usual method of auto-regulation e.g. for tcp. You've written latency isn't
so much problem, then slightly overloading ISP's queue you'll always get full
bandwidth, you've payed for. You didn't write what kind of traffic you service,
but I doubt you can get rid of dropping everywhere: on your HTB etc. queues
or on incoming traffic.

> [...] This means something wrong or in my shaping tree configuration 
> (that time HTB) or in shaper code. Thats why i try to dig in this things more 
> deeply.

Did you try to dig at this very nice HTB page?:
http://luxik.cdi.cz/~devik/qos/htb/

Regards,
Jarek P.

  reply	other threads:[~2007-11-20 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  8:55 HTB/HSFC shaping precision Denys Fedoryshchenko
2007-11-19 16:24 ` jamal
2007-11-20  9:43   ` Denys Fedoryshchenko
2007-11-20 20:00     ` Jarek Poplawski [this message]
2007-11-20 21:21       ` Denys Fedoryshchenko
2007-11-21  9:47         ` Jarek Poplawski
2007-11-21 10:31           ` Denys Fedoryshchenko
2007-11-21 15:06             ` jamal
2007-11-22  2:07               ` Ryousei Takano

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=47433CF8.70501@o2.pl \
    --to=jarkao2@o2.pl \
    --cc=denys@visp.net.lb \
    --cc=hadi@cyberus.ca \
    --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;
as well as URLs for NNTP newsgroup(s).