From: Chris Friesen <chris.friesen@genband.com>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: frog1120@gmail.com, "J.Hwan.Kim" <j.hwan.kim99@gmail.com>,
netdev <netdev@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: intel 82599 multi-port performance
Date: Mon, 26 Sep 2011 10:40:24 -0600 [thread overview]
Message-ID: <4E80AAF8.1000806@genband.com> (raw)
In-Reply-To: <4E80A2AB.2040206@intel.com>
On 09/26/2011 10:04 AM, Alexander Duyck wrote:
> It sounds like you are using a single card, would that be correct? If
> you are running close to line rate on both ports this could be causing
> you to saturate the PCIe x8 link.
According to
"http://communities.intel.com/community/wired/blog/2009/06/08/understanding-pci-express-bandwidth"
8x PCIe should have a bandwidth of 4GB/s. 2 10Gigabit ports is 2.5GB/s.
The 82599 only goes up to 8x, so I'd expect that it should be sufficient
to handle the full traffic.
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?
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-09-26 16:42 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 [this message]
2011-09-26 17:24 ` [E1000-devel] " Ben Greear
2011-09-26 17:46 ` Chris Friesen
2011-09-26 17:57 ` Ben Greear
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=4E80AAF8.1000806@genband.com \
--to=chris.friesen@genband.com \
--cc=alexander.h.duyck@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=frog1120@gmail.com \
--cc=j.hwan.kim99@gmail.com \
--cc=jeffrey.t.kirsher@intel.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.