From: "François-Frédéric Ozog" <ff@ozog.com>
To: "'Michael Quicquaro'" <michael.quicquaro@gmail.com>, <dev@dpdk.org>
Cc: mayhan@mayhan.org
Subject: Re: [dpdk-dev] Rx-errors with testpmd (only 75% line rate)
Date: Thu, 9 Jan 2014 22:21:27 +0100 [thread overview]
Message-ID: <013e01cf0d80$c26d9450$4748bcf0$@com> (raw)
In-Reply-To: <CAAD-K97KDoGVow6dVrKdRtCyD+wgJchO4OJFpGTRDgiaq5=Stw@mail.gmail.com>
Hi,
Can you check that the threads you use for handling the queues are on the
same socket as the card ?
cat /sys/class/net/<interface name>/device/numa_node
will give you the node.
François-Frédéric
> -----Message d'origine-----
> De : dev [mailto:dev-bounces@dpdk.org] De la part de Michael Quicquaro
> Envoyé : jeudi 9 janvier 2014 20:28
> À : dev@dpdk.org
> Cc : mayhan@mayhan.org
> Objet : [dpdk-dev] Rx-errors with testpmd (only 75% line rate)
>
> Hello,
> My hardware is a Dell PowerEdge R820:
> 4x Intel Xeon E5-4620 2.20GHz 8 core
> 16GB RDIMM 1333 MHz Dual Rank, x4 - Quantity 16 Intel X520 DP 10Gb DA/SFP+
>
> So in summary 32 cores @ 2.20GHz and 256GB RAM
>
> ... plenty of horsepower.
>
> I've reserved 16 1GB Hugepages
>
> I am configuring only one interface and using testpmd in rx_only mode to
> first see if I can receive at line rate.
>
> I am generating traffic on a different system which is running the netmap
> pkt-gen program - generating 64 byte packets at close to line rate.
>
> I am only able to receive approx. 75% of line rate and I see the Rx-errors
> in the port stats going up proportionally.
> I have verified that all receive queues are being used, but strangely
> enough, it doesn't matter how many queues more than 2 that I use, the
> throughput is the same. I have verified with 'mpstat -P ALL' that all
> specified cores are used. The utilization of each core is only roughly
> 25%.
>
> Here is my command line:
> testpmd -c 0xffffffff -n 4 -- --nb-ports=1 --coremask=0xfffffffe
> --nb-cores=8 --rxd=2048 --txd=2048 --mbcache=512 --burst=512 --rxq=8
> --txq=8 --interactive
>
> What can I do to trace down this problem? 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.
>
> Thanks for any help.
> - Michael
next prev parent reply other threads:[~2014-01-09 21:22 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 [this message]
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
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='013e01cf0d80$c26d9450$4748bcf0$@com' \
--to=ff@ozog.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).