From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] The effects of queueing on delay...(TX Ring Buffer the
Date: Mon, 17 Oct 2005 19:20:43 +0000 [thread overview]
Message-ID: <4353F98B.8020709@dsl.pipex.com> (raw)
In-Reply-To: <1129064647.13493.41.camel@pgala.it.nuigalway.ie>
Jonathan Lynch wrote:
> This was down to the tx buffer size on the network card i was using. It
> was an Intel 82547EI gigabit Card using the e1000 driver and operating
> at 100mbit. The tx buffer was set to 256 which caused this huge delay.
> The minimum the driver lets me reduce the tx buffer size using ethtool
> is 80. By reducing the tx ring buffer to 80, the delay when there is
> full link utilisation and a maximum queue of 10 packets was reduced from
> 30ms to 10ms.
>
> The 3com 3c59x vortex driver uses a tx buffer of 16. I reduced the tx to
> 16 on the e1000 driver, but the max throughput i could achieve on the
> interface went down.
>
> Has anyone experimented with reducing the size of the tx buffer on this
> card to get a good balance between delay and throughput ?
Strange - I thought that as long as you are under rate for the link then
the most htb should burst per tick is the burst size specified.
That assumes one bulk class - more will make it worse.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-17 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:04 [LARTC] The effects of queueing on delay Jonathan Lynch
2005-10-13 16:06 ` [LARTC] The effects of queueing on delay...(TX Ring Buffer the Jonathan Lynch
2005-10-17 19:20 ` Andy Furniss [this message]
2005-11-19 23:53 ` Jonathan Lynch
2005-12-06 1:55 ` 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=4353F98B.8020709@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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