All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] egress bandwidth not limited / limited extremely
Date: Wed, 17 Jan 2007 21:11:46 +0000	[thread overview]
Message-ID: <45AE9112.2000703@andyfurniss.entadsl.com> (raw)
In-Reply-To: <45AC22ED.4060107@skula.com>

Marek Kierdelewicz wrote:
> Hi there,
> 
> 
>>>05:04.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5714
>>>Gigabit Ethernet (rev a3)
> 
> 
>>You may need to turn off segmentation offload with ethtool -k
> 
> 
> That's very interesting. Do you have any more information on this
> subject? Does tso in general distrupt accuracy of tc ops or is it the
> case only with Broadcom nics? Any links would be very much appreciated.

I don't have any gig eth, but it's not just Broadcom.

There have been other posts on here where people have needed to increase 
  htb's mtu parameter to get htb to handle it - despite the interface 
being 1500. For shaping traffic for a slow link that is not going to be 
nice - you could end up dropping multiple tcp segments at once, and it 
will hurt jitter. I don't imagine it's right to do it for shaping at gig 
speed either, maybe the default long queue on eth saves dropping.

I suppose those using gig eth and shaping routed traffic at 1500 MTU 
will not notice unless they try and shape locally generated aswell.

Andy.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-01-17 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16  0:57 [LARTC] egress bandwidth not limited / limited extremely Roman Skula
2007-01-16 14:53 ` [LARTC] egress bandwidth not limited / limited Andy Furniss
2007-01-16 17:05 ` [LARTC] egress bandwidth not limited / limited extremely Roman Skula
2007-01-17 11:12 ` Marek Kierdelewicz
2007-01-17 21:11 ` Andy Furniss [this message]
2007-01-17 21:18 ` [LARTC] egress bandwidth not limited / limited 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=45AE9112.2000703@andyfurniss.entadsl.com \
    --to=lists@andyfurniss.entadsl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.