From: George Yaneff <gesha2@abv.bg>
To: users@dpdk.org
Subject: [dpdk-users] DPDK Distributor app issues
Date: Mon, 10 Jun 2019 17:40:14 +0300 (EEST) [thread overview]
Message-ID: <1567292027.2330305.1560177614329@nm22.abv.bg> (raw)
I'm playing with the distributor example application from dpdk 19.05.0 I have three machines connected sequentially with an UTP Ethernet cable. The
middle is Ubuntu 18.04.2 LTS with a eigth core Intel I7 processor and 24 GB ram. The eth device used is Intel I350 with four ports.
The strange behavior I'm observing is when I ping the second node from the first node (traffic passing through the distributor) there are always one or two packets lost.
When I use
l2fwd or
basicfwd applications there is no packet loss. Anyone knows if this is normal or if it is not - what I'm doing wrong?
Another thing I noticed is that the ping replies come to the first node with around one second of delay. (1024ms on most packets) Again there is no latency with the basicfwd (packets arriving in 0.101 ms there). Is there any way to minimize this delay in distributor application also?
George
next reply other threads:[~2019-06-10 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 14:40 George Yaneff [this message]
2019-06-10 16:13 ` Van Haaren, Harry
2019-06-11 6:40 ` George Yaneff
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=1567292027.2330305.1560177614329@nm22.abv.bg \
--to=gesha2@abv.bg \
--cc=users@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).