DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yerden Zhumabekov <e_zhumabekov@sts.kz>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] pcap->eth low TX performance
Date: Fri, 4 Sep 2015 10:14:42 +0600	[thread overview]
Message-ID: <55E91AB2.4080604@sts.kz> (raw)

Hello,

Did anyone try to work with pcap PMD recently? We're testing our app
with this setup:

PCAP --- rte_eth_rx_burst--> APP-> rte_eth_tx_burst -> ethdev

I'm experiencing very low TX performance leading to massive mbuf drop
while trying to send those packets over the Ethernet device. I tried
running ordinary l2fwd and got the same issue with over 80-90% of
packets drop. When I substitute PCAP with another ordinary Ethernet
device, everything works fine. Can anyone share an idea?

-- 
Sincerely,

Yerden Zhumabekov
State Technical Service
Astana, KZ

             reply	other threads:[~2015-09-04  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  4:14 Yerden Zhumabekov [this message]
2015-09-04 14:03 ` Kyle Larose
2015-09-07  2:40   ` Yerden Zhumabekov

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=55E91AB2.4080604@sts.kz \
    --to=e_zhumabekov@sts.kz \
    --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).