From: Laurent Dumont <laurentfdumont@gmail.com>
To: users@dpdk.org
Subject: DPDK and packet loss troubleshooting
Date: Sat, 7 May 2022 12:55:18 -0400 [thread overview]
Message-ID: <CAOAKi8xHgVZmEWOLZ9zsD93G6JA2N6jMEZ9sPxV2K43e0Cm4cQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hey folks,
We are troubleshooting a vendor application that is leveraging DPDK at the
application layer.
- Openstack with RHOSP / RHEL
- OVS as the underlying virtual switching layer. *The VM is not using
SRIOV ports.*
- VM acts as a load balancer (traffic pattern in IN+OUT). Traffic
arrives on a VLAN (provider network) and exits through a VXLAN network
(internal) to be forwarded to application servers.
- VMs are using pinned cores
- 4 cores total
- 2 for the OS
- 2 for DPDK : 1 TX one RX
- Using hugepages
- There are no other VMs on the physical compute.
- compute is using isolated cores for the OS. No collision with the VM
cores.
At low packet rates (20k~ PPS), it seems that the DPDK layer fails to
transmit packets on the TX queue. This triggers a failover.
We are not seeing anything particularly obvious on the compute side. Is
there anything at the DPDK layer that should be clear about why there is a
failure to TX?
Thanks!
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
reply other threads:[~2022-05-07 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOAKi8xHgVZmEWOLZ9zsD93G6JA2N6jMEZ9sPxV2K43e0Cm4cQ@mail.gmail.com \
--to=laurentfdumont@gmail.com \
--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).