From: Armin Steinhoff <as@steinhoff-automation.com>
To: dev@dpdk.org
Subject: [dpdk-dev] i210 performance ?
Date: Tue, 12 Nov 2013 09:51:20 +0100 [thread overview]
Message-ID: <5281EC08.9060408@steinhoff-automation.com> (raw)
In-Reply-To: <mailman.0.1384159076.18289.dev@dpdk.org>
Hi All,
after porting Intel's Data Plan to QNX 6.5 I'm doing some performance
test with "testpmd".
I'm using a single i210 board installed on a dual core QNX 6.5 machine
and using "testpmd" as a packet generator (UDP packets).
The test are done with:
start: testpmd -c 3 -n -> interactive mode by default
set burst 1
set fwd txonly
start
stop
Without a delay between packets I see a huge number of dropped packets.
After introducing a delay of 60us after sending the "packet burst"
dropping of packets doesn't happen.
My questions are: why dropps the i210 packets ? Is it because of the
fact that probably all send descriptors are occupied ?
Best Regards
Armin Steinhoff
parent reply other threads:[~2013-11-12 8:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.0.1384159076.18289.dev@dpdk.org>]
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=5281EC08.9060408@steinhoff-automation.com \
--to=as@steinhoff-automation.com \
--cc=dev@dpdk.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 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).