From: Bugzilla-Redirect <bugzilla@sysreset.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: htb traffic shaping problem
Date: Tue, 19 Sep 2006 02:42:07 +0000 [thread overview]
Message-ID: <6.2.0.14.2.20060918204013.031a9e18@linux.sysreset.com> (raw)
In-Reply-To: <6.2.0.14.2.20060912225307.02dd8f98@linux.sysreset.com>
I was not aware that segmentation offloading would cause a problem... and I
do believe it's on.
I think I'll just stuck with the high mtu for the moment then, as I would
rather have the CPU savings
then more accurate traffic controlling.
Thanks.
-Ryan Power
At 07:48 AM 9/18/2006, Andy Furniss wrote:
>gypsy wrote:
>>Bugzilla-Redirect wrote:
>>
>>>Yes, the output is below:
>>>eth0 Link encap:Ethernet HWaddr 00:11:09:2A:A6:F6
>>> inet addr:10.0.0.50 Bcast:10.0.0.255 Mask:255.255.255.0
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:4244867 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:1306632 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes:3898905509 (3.6 GiB) TX bytes:1756030081 (1.6 GiB)
>>> Interrupt:19
>>
>>Try a "quantum 1514" then; that is correct for an ethernet device with
>>an MTU of 1500.
>>Perhaps reading the source code will give a clue about MPU and MTU?
>>Frankly, I'd set it to whatever works as long as the rest of the status
>>info looks right and not give a damn that it is huge.
>
>Even if ifconfig says 1500 there have been posts that say you don't get it
>with gig cards that do segmentation offload unless you can turn it off
>with ethtool.
>
>Apologies if this has already been said as I don't have all the thread.
>
>Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-09-19 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 4:59 [LARTC] Re: htb traffic shaping problem Bugzilla-Redirect
2006-09-14 10:53 ` e.janz
2006-09-16 1:38 ` Bugzilla-Redirect
2006-09-16 16:20 ` gypsy
2006-09-18 13:48 ` Andy Furniss
2006-09-19 2:42 ` Bugzilla-Redirect [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=6.2.0.14.2.20060918204013.031a9e18@linux.sysreset.com \
--to=bugzilla@sysreset.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