From: Ben Greear <greearb@candelatech.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: "e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
netdev <netdev@vger.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"J.Hwan.Kim" <j.hwan.kim99@gmail.com>,
frog1120@gmail.com
Subject: Re: intel 82599 multi-port performance
Date: Mon, 26 Sep 2011 10:57:52 -0700 [thread overview]
Message-ID: <4E80BD20.2040301@candelatech.com> (raw)
In-Reply-To: <4E80BA91.2040803@genband.com>
On 09/26/2011 10:46 AM, Chris Friesen wrote:
> On 09/26/2011 11:24 AM, Ben Greear wrote:
>> On 09/26/2011 09:40 AM, Chris Friesen wrote:
>
>>> To any of the Intel guys out there...any ideas? Can an 82599 on an 8x
>>> bus handle max line rate with minimum size packets?
>>
>> Rick Jones sent me an interesting link related to this. Short answer seems
>> to be 'yes', but it seems not for any normal off-the-shelf software stack.
>>
>> > This: http://comments.gmane.org/gmane.linux.network/203602 should
>> lead you to some slide.
>
> Interesting. I wonder if Intel's DPDK will be the only way to handle those sorts of packet rates.
Pktgen is probably still the fastest general code that I know of,
but we had some interesting results setting the TCP_MAXSEGS to
88, which creates around 150 byte packets, and let the NICs offload
chop up large TCP writes into small packets on the wire.
Using core-I7 980x CPU, and dual-port 82599, we could send
around 4Mpps and receive around 2Mpps between two machines.
We were using a single port on each NIC/machine for this test. Connection
was a bit asymmetric, seems one side would over-power the other...so if
we twiddled a bit, we could get around 3Mpps in each direction.
Our user-space app has some over-head as well, but we can send
at least 5Gbps full duplex on two ports using normal sized frames, so I
think the bottleneck in this case is the TCP offload in the NIC.
Still, pretty impressive for stateful TCP packets per second :)
Top-of-tree netperf just learned to do the TCP_MAXSEG trick as well,
so it might be fun to play with that. It probably has less overhead
than our tool, so might run even faster.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2011-09-26 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 10:26 intel 82599 multi-port performance J.Hwan Kim
2011-09-26 14:20 ` Chris Friesen
2011-09-26 15:42 ` J.Hwan.Kim
2011-09-26 16:04 ` Alexander Duyck
2011-09-26 16:40 ` Chris Friesen
2011-09-26 17:24 ` [E1000-devel] " Ben Greear
2011-09-26 17:46 ` Chris Friesen
2011-09-26 17:57 ` Ben Greear [this message]
2011-09-27 0:45 ` J.Hwan Kim
2011-09-27 15:30 ` Martin Millnert
2011-09-27 17:14 ` Alexander Duyck
2011-09-27 22:57 ` Chris Friesen
2011-09-26 18:16 ` Rick Jones
2011-09-27 0:39 ` J.Hwan Kim
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=4E80BD20.2040301@candelatech.com \
--to=greearb@candelatech.com \
--cc=chris.friesen@genband.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=frog1120@gmail.com \
--cc=j.hwan.kim99@gmail.com \
--cc=jesse.brandeburg@intel.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.