From: Yerden Zhumabekov <e_zhumabekov@sts.kz>
To: Kyle Larose <eomereadig@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] pcap->eth low TX performance
Date: Mon, 7 Sep 2015 08:40:59 +0600 [thread overview]
Message-ID: <55ECF93B.9020000@sts.kz> (raw)
In-Reply-To: <CAMFWN9n4hfTgBLpZKdU5j=q_wE4nkXdjY-cT3MeBnXMPhTLTeA@mail.gmail.com>
tx burst sends, say, 10-15% percent of a supplied array. The tail is
being ignored so I have to drop it to avoid overflow.
Ethernet device is 82599.
In my app, I transmit all traffic through a ring then feed it to eth.
That leads to overflow as well.
04.09.2015 20:03, Kyle Larose пишет:
> Are you reading from the pcap faster than the device can transmit?
> Does the app hold off reading from the pcap when the ethdev is pushing
> back, or does it just tail drop?
>
> On Fri, Sep 4, 2015 at 12:14 AM, Yerden Zhumabekov
> <e_zhumabekov@sts.kz <mailto:e_zhumabekov@sts.kz>> wrote:
>
> 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
>
>
--
Sincerely,
Yerden Zhumabekov
State Technical Service
Astana, KZ
prev parent reply other threads:[~2015-09-07 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 4:14 Yerden Zhumabekov
2015-09-04 14:03 ` Kyle Larose
2015-09-07 2:40 ` Yerden Zhumabekov [this message]
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=55ECF93B.9020000@sts.kz \
--to=e_zhumabekov@sts.kz \
--cc=dev@dpdk.org \
--cc=eomereadig@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).