From: Jesper Krogh <jesper@krogh.cc>
To: David Miller <davem@davemloft.net>
Cc: Matheos.Worku@Sun.COM, yhlu.kernel@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24)
Date: Thu, 22 May 2008 18:32:07 +0200 [thread overview]
Message-ID: <4835A007.7020601@krogh.cc> (raw)
In-Reply-To: <20080509.154538.28321777.davem@davemloft.net>
David Miller wrote:
> From: Matheos Worku <Matheos.Worku@Sun.COM>
> Date: Fri, 09 May 2008 15:36:17 -0700
>
>> I have observed TX throughput degradation (and increased CPU
>> utilization) occurs with increased # of connections, when CPU count > 4
>> CPUs. I don't think it is related to the driver (or HW).
>
> All transmits through a device are fully serialized currently,
> it's a known problem and something we plan to fix.
I google'd up this one:
http://vger.kernel.org/~davem/davem_tokyo08.pdf (slide 23+).
Does this mean that I can expect every 10G card to have this limitation
under Linux? Or are some known to be better than others?
(I can probably justify paying for another 10G card if I can expect to
gain the last 400MB/s).
Since I cannot push more than ~600MB/s through the NIC before a single
cpu is bottlenecked, it seem most likely to be this TX throughput
thing I hit.
Thanks
Jesper
--
Jesper
next prev parent reply other threads:[~2008-05-22 16:32 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:23 NIU - Sun Neptune 10g - Transmit timed out reset (2.6.24) Jesper Krogh
2008-05-07 18:30 ` Yinghai Lu
2008-05-07 21:15 ` David Miller
2008-05-09 18:32 ` Jesper Krogh
2008-05-09 21:32 ` David Miller
2008-05-09 21:59 ` Jesper Krogh
2008-05-09 22:07 ` David Miller
2008-05-09 22:13 ` Jesper Krogh
2008-05-09 22:09 ` Matheos Worku
2008-05-09 22:15 ` Jesper Krogh
2008-05-09 22:36 ` Matheos Worku
2008-05-09 22:43 ` Matheos Worku
2008-05-09 22:46 ` David Miller
2008-05-09 23:10 ` Jesper Krogh
2008-05-09 23:21 ` Matheos Worku
2008-05-09 22:45 ` David Miller
2008-05-22 16:32 ` Jesper Krogh [this message]
2008-05-22 17:15 ` Ben Hutchings
2008-05-22 17:41 ` David Miller
2008-05-22 18:14 ` Ben Hutchings
2008-05-22 18:28 ` David Miller
2008-06-01 7:25 ` Andrey Panin
2008-06-01 16:01 ` David Miller
2008-05-09 22:20 ` Rick Jones
2008-05-09 22:48 ` Jesper Krogh
2008-05-09 23:03 ` Rick Jones
2008-05-09 23:13 ` Jesper Krogh
2008-05-09 23:33 ` Rick Jones
2008-05-09 23:08 ` David Dillow
2008-05-10 6:22 ` Jesper Krogh
2008-05-10 15:53 ` Roland Dreier
2008-05-12 6:49 ` Jesper Krogh
2008-05-10 2:20 ` Bill Fink
2008-05-10 11:01 ` Jesper Krogh
2008-05-11 4:34 ` David Miller
2008-05-11 5:44 ` Jesper Krogh
2008-05-11 6:08 ` David Miller
2008-05-11 9:47 ` Jesper Krogh
2008-05-12 6:52 ` Jesper Krogh
2008-05-26 19:03 ` Jesper Krogh
2008-05-26 19:33 ` David Miller
2008-05-26 19:39 ` David Miller
2008-05-26 20:54 ` Jesper Krogh
2008-05-26 22:15 ` David Miller
2008-05-26 22:21 ` Jesper Krogh
2008-05-26 22:30 ` David Miller
2008-05-27 6:19 ` Jesper Krogh
2008-05-28 1:18 ` Matheos Worku
2008-05-29 5:34 ` David Miller
2008-05-30 0:14 ` Matheos Worku
2008-05-30 7:00 ` David Miller
2008-06-16 18:09 ` Matheos Worku
2008-06-16 18:21 ` Jesper Krogh
2008-06-18 0:02 ` David Miller
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=4835A007.7020601@krogh.cc \
--to=jesper@krogh.cc \
--cc=Matheos.Worku@Sun.COM \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/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.