From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Clock Source Kernel settings in 2.6.22
Date: Sun, 02 Sep 2007 11:45:42 +0000 [thread overview]
Message-ID: <46DAA266.8070601@trash.net> (raw)
In-Reply-To: <45E4FD623F464B30A0067FF269007B89@shadow>
[Please keep me in CC/To, I don't read lartc often]
Mario Antonio Garcia wrote:
> I used to get an average of 18900kbit.
> My hope was that these new patches would bring better accuracy.
Well, you're up from 94.5% to 99.95%, so they seem to do :)
> Notice the 24 cburst. I am just trying to compensate the inaccuracy
> this way. If I remove the cburst, obviously the shape rate I get goes
> down.
>
> Perhaps I am missing something. I am just a novice trying to get
> exact bandwidth shaping. I have tested all the clock source types with
> no good results.
A couple of comments:
- The patches so far only improve things on x86
- Try to test using UDP (not sure if you did) or simply a ping flood,
TCP is not ideal.
- iproute calculates burst values automatically. With the higher
precision clock source you can use a smaller value (also done
automatically if you don't specify them).
- HFSC is more precise than HTB (and not the least more complicated
to configure if you use only linear service curves)
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-09-02 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 13:24 [LARTC] Clock Source Kernel settings in 2.6.22 Mario Antonio Garcia
2007-08-31 9:43 ` Patrick McHardy
2007-08-31 18:46 ` Mario Antonio Garcia
2007-09-02 11:45 ` Patrick McHardy [this message]
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=46DAA266.8070601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox