From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: netdev@vger.kernel.org
Subject: HTB/HSFC shaping precision
Date: Mon, 19 Nov 2007 10:55:17 +0200 [thread overview]
Message-ID: <20071119083849.M87605@visp.net.lb> (raw)
Hi 2 all again
This is not a bug report this time :-)
Just it is very interesting question, about using Linux "shaping" technologies
in serious jobs.
What i realised few days ago, many ISP's set on their STM-1(155520000 bits/s)
links (over Cisco) packet buffer/queue 40 packets(for example).
It means 103680 pps with 1500 byte packets, and if buffer is only 40
packets, it means it require at least 0.3ms scheduler precision? Otherwise i
can have buffer overflow and as result packetloss(what is much worse than
delay in most of situations).
What i am interested - to utilise such links nearby 100%. So anything not
precise will kill idea.
Thats important, cause price for links in my area is about $1000-$1500 Mbit/s,
and just 1% lost/not utilised on STM-1 is up to $2325/USD lost per month.
I have to count also overhead, LAN jitter, and etc.
As far as i test, on HFSC if i set dmax 1ms-10ms it works much better (i am
talking about precision) than HTB with quantum 1514 (it is over ethernet).
Anybody have ideas what is the precision of bandwidth shaping in HFSC/HTB?
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next reply other threads:[~2007-11-19 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 8:55 Denys Fedoryshchenko [this message]
2007-11-19 16:24 ` HTB/HSFC shaping precision jamal
2007-11-20 9:43 ` Denys Fedoryshchenko
2007-11-20 20:00 ` Jarek Poplawski
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=20071119083849.M87605@visp.net.lb \
--to=denys@visp.net.lb \
--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).