All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb overrate with 2.6.16
Date: Mon, 17 Apr 2006 19:32:49 +0000	[thread overview]
Message-ID: <4443ED61.80902@trash.net> (raw)
In-Reply-To: <1145095091.18168.26.camel@indigo.declera.com>

Andy Furniss wrote:
>> Well, as much as google tells me TSO has been in the kernel and enabled
>> since 2.5.33 and e1000 was the first driver to support it. The FC4
>> 2.6.16 kernel doesn't have any tso related patches as can be
>> seen here http://cvs.fedora.redhat.com/viewcvs/rpms/kernel/FC-4/
>>
>> Since my immediate problem was solved with the mtu param I plan on
>> forgetting about htb and traffic control in general for the time
>> being :) Thanks again.
> 
> 
> One more thing I just thought - sfq sets its quantum from the dev mtu.

One more possibility: current kernels support UDP fragmentation offload
(UFO), which has similar effects as TSO. The in-tree e1000 driver
doesn't support it, but maybe the fedora one does.

Changes in the fragmentation behaviour of conntrack in 2.6.16 could also
be responsible (if you're using it). Can you please post your NAT and
marking rules, routing rules etc?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-04-17 19:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15  9:58 [LARTC] htb overrate with 2.6.16 Yanko Kaneti
2006-04-15 23:13 ` Andy Furniss
2006-04-16  0:19 ` Yanko Kaneti
2006-04-16  2:03 ` Andy Furniss
2006-04-16  2:37 ` Yanko Kaneti
2006-04-16 18:40 ` Andy Furniss
2006-04-16 20:03 ` Yanko Kaneti
2006-04-16 21:10 ` Andy Furniss
2006-04-17 19:03 ` Andy Furniss
2006-04-17 19:32 ` Patrick McHardy [this message]
2006-04-17 21:02 ` Yanko Kaneti
2006-04-18 11:25 ` Andy Furniss
2006-04-18 11:36 ` Andy Furniss
2006-04-18 13:05 ` 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=4443ED61.80902@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 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.