netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ryousei Takano <ryousei@gmail.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	Patrick McHardy <kaber@trash.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	takano-ryousei@aist.go.jp
Subject: Re: HTB accuracy on 10GbE
Date: Wed, 04 Nov 2009 06:03:25 +0100	[thread overview]
Message-ID: <4AF10B1D.4050604@gmail.com> (raw)
In-Reply-To: <b30d1c3b0911031913k2c922935vc9605b76ac43168f@mail.gmail.com>

Ryousei Takano a écrit :
> Hi Patrick and Stephen,
> 
> Thanks for your comments.
> 
> I retried on the newer kernel and iproute2, and added the experimental result
> on my page.  Please see 'Experimental result 2':
>     http://code.google.com/p/pspacer/wiki/HTBon10GbE
> 
> The accuracy improves compared with the previous experiment.
> The difference reduces from +810 Mbps to +430 Mbps.
> It is because the timer resolution improves from 1 usec to 1/64 usec.
> But it is not perfect.
> 

Hmm, do you know part of the error comes from the user tool itself ?

If you check iperf results at sender and receiver you'll see different
values, sender lies a bit.

Tried here on a Gbit link (I dont have 10Gbe yet)

$ ./iperf.bench.sh
.100 104
.200 206
.300 307
.400 413
.500 515
.600 610
.700 715
.800 822
.900 913
1.000 945

while on receiver :
[  4]  0.0- 5.3 sec  62.8 MBytes    100 Mbits/sec
[  5]  0.0- 5.1 sec    123 MBytes    202 Mbits/sec
[  4]  0.0- 5.1 sec    183 MBytes    303 Mbits/sec
[  5]  0.0- 5.1 sec    246 MBytes    409 Mbits/sec
[  4]  0.0- 5.0 sec    307 MBytes    511 Mbits/sec
[  5]  0.0- 5.0 sec    364 MBytes    607 Mbits/sec
[  4]  0.0- 5.0 sec    427 MBytes    711 Mbits/sec
[  5]  0.0- 5.0 sec    490 MBytes    818 Mbits/sec
[  4]  0.0- 5.0 sec    545 MBytes    909 Mbits/sec
[  5]  0.0- 5.0 sec    565 MBytes    941 Mbits/sec


You might use longer intervals to reduce this error (10 secs instead of 5 secs)

$./iperf.bench.sh
.100 102
.200 204
.300 305
.400 410
.500 513
.600 608
.700 713
.800 820
.900 911
1.000 943

  parent reply	other threads:[~2009-11-04  5:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  7:22 HTB accuracy on 10GbE Ryousei Takano
2009-11-02  8:17 ` Badalian Vyacheslav
2009-11-02 15:43 ` Patrick McHardy
2009-11-02 20:53   ` Stephen Hemminger
2009-11-03  7:43     ` Badalian Vyacheslav
2009-11-03  9:33       ` Jarek Poplawski
2009-11-03 10:13         ` Badalian Vyacheslav
2009-11-03 10:54           ` Jarek Poplawski
2009-11-03 11:13             ` Badalian Vyacheslav
2009-11-04  3:13     ` Ryousei Takano
2009-11-04  3:45       ` Ryousei Takano
2009-11-04  5:03       ` Eric Dumazet [this message]
2009-11-04  5:27         ` Eric Dumazet
2009-11-04  8:19           ` Ryousei Takano
2009-11-04 11:31             ` Eric Dumazet
2009-11-04 13:39               ` Jarek Poplawski
2009-11-04 16:31               ` Ryousei Takano
2009-11-04 17:03                 ` Eric Dumazet
2009-11-05  7:08                   ` Ryousei Takano
2009-11-05  7:10                     ` Eric Dumazet
2009-11-05 10:15                       ` 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=4AF10B1D.4050604@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=ryousei@gmail.com \
    --cc=shemminger@vyatta.com \
    --cc=takano-ryousei@aist.go.jp \
    /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).