From: Robert Sanford <rsanford@prolexic.com>
To: Michael Quicquaro <michael.quicquaro@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, mayhan@mayhan.org
Subject: Re: [dpdk-dev] Rx-errors with testpmd (only 75% line rate)
Date: Wed, 22 Jan 2014 15:38:12 -0500 [thread overview]
Message-ID: <CAFmpvUNHqpp0DhsFXtYQOxDObV_K5Qs2B=w7miynMADpP21C5A@mail.gmail.com> (raw)
In-Reply-To: <CAAD-K97KDoGVow6dVrKdRtCyD+wgJchO4OJFpGTRDgiaq5=Stw@mail.gmail.com>
Hi Michael,
> What can I do to trace down this problem?
May I suggest that you try to be more selective in the core masks on the
command line. The test app may choose some cores from "other" CPU sockets.
Only enable cores of the one socket to which the NIC is attached.
> It seems very similar to a
> thread on this list back in May titled "Best example for showing
> throughput?" where no resolution was ever mentioned in the thread.
After re-reading *that* thread, it appears that their problem may have been
trying to achieve ~40 Gbits/s of bandwidth (2 ports x 10 Gb Rx + 2 ports x
10 Gb Tx), plus overhead, over a typical dual-port NIC whose total bus
bandwidth is a maximum of 32 Gbits/s (PCI express 2.1 x8).
--
Regards,
Robert
next prev parent reply other threads:[~2014-01-22 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 19:28 Michael Quicquaro
2014-01-09 21:21 ` François-Frédéric Ozog
2014-01-22 14:52 ` Dmitry Vyal
2014-01-22 17:46 ` Wang, Shawn
2014-01-27 20:00 ` Michael Quicquaro
2014-01-28 8:31 ` Dmitry Vyal
2014-02-10 17:34 ` Jun Han
2014-01-22 20:38 ` Robert Sanford [this message]
2014-01-23 23:22 ` Michael Quicquaro
2014-01-24 9:18 ` François-Frédéric Ozog
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='CAFmpvUNHqpp0DhsFXtYQOxDObV_K5Qs2B=w7miynMADpP21C5A@mail.gmail.com' \
--to=rsanford@prolexic.com \
--cc=dev@dpdk.org \
--cc=mayhan@mayhan.org \
--cc=michael.quicquaro@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).