From: Howard Chu <hyc@highlandsun.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.3 network slowdown?
Date: Wed, 27 Jul 2005 12:42:16 -0700 [thread overview]
Message-ID: <42E7E398.7000308@highlandsun.com> (raw)
In-Reply-To: <20050727105506.78b82aaa@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> On Wed, 27 Jul 2005 01:44:43 -0700
> Howard Chu <hyc@highlandsun.com> wrote:
>> I just recently compiled the 2.6.12.3 kernel for my x86_64 machine
>> (Asus A8V motherboard); was previously running a SuSE-compiled 2.6.8
>> kernel (SuSE 9.2 distro). I'm now seeing extremely slow throughput on
>> the onboard Yukon (Marvell) ethernet interface, but only in certain
>> conditions. Going back to the 2.6.8 kernel shows no slowdown.
> There a couple of possibilities, one is driver differences. SUSE ships
> the SysKonnect vendor driver vs the older version in 2.6.12, and the
> TCP congestion and TSO code has changed since 2.6.8.
Thanks for that tip. The SuSE 2.6.8 kernel had driver version 7.04, the
2.6.12.3 kernel had driver version 6.23. I just downloaded the current
driver from www.syskonnect.de (8.23) and installed it and now things are
much improved, getting around 6.8MB/sec throughput.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/
prev parent reply other threads:[~2005-07-27 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1122452018.772579.63900@g49g2000cwa.googlegroups.com>
[not found] ` <20050727082020.C73AC5F7CA@attila.bofh.it>
2005-07-27 8:44 ` 2.6.12.3 network slowdown? Howard Chu
2005-07-27 10:30 ` Mihai Rusu
2005-07-27 13:00 ` Bernd Schubert
2005-07-27 17:55 ` Stephen Hemminger
2005-07-27 19:42 ` Howard Chu [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=42E7E398.7000308@highlandsun.com \
--to=hyc@highlandsun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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