From: Andi Kleen <andi@firstfloor.org>
To: "Hua Zhong" <hzhong@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Linux 2.6 HTB does only work with existing connections
Date: 22 Feb 2007 14:47:38 +0100 [thread overview]
Message-ID: <p73lkiqcnid.fsf@bingen.suse.de> (raw)
In-Reply-To: <01e001c7562e$9d452ff0$d7cf8fd0$@com>
"Hua Zhong" <hzhong@gmail.com> writes:
> Correction: it's TSO, not TOE.
>
> By googling I found that specifying a big MTU (like 16500) on the "tc class"
> command avoids the "giant" packets. No idea where they come from.
They come from TCP because it will pass down a max MTU sized packet
(upto 64k) for the NIC to segment (Tcp Segmentation Offload)
But the traffic control cannot work with such large packets.
> Any better idea on a proper fix?
Hmm, that's nasty. The only workaround I could think of would
be to force TSO/LSO off when a non standard queueing discipline is active.
-Andi
next prev parent reply other threads:[~2007-02-22 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 3:07 Linux 2.6 HTB does only work with existing connections Hua Zhong
2007-02-22 13:47 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 2:30 Hua Zhong
2007-02-22 13:45 ` Andi Kleen
2007-02-22 1:44 Hua Zhong
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=p73lkiqcnid.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=hzhong@gmail.com \
--cc=netdev@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.