From: Dheeraj Dang <dheerajdang138@gmail.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Packet Drop in same NUMA
Date: Sat, 2 Mar 2019 08:02:11 +0530 [thread overview]
Message-ID: <CAJyVW4-i6rhC1dVe+MSwejd8hCNwDNusC0pR7Op7CK+-mXOLfQ@mail.gmail.com> (raw)
Hi all,
I m facing one issue in which packets are continuously dropped at vhost
level in same numa configuration.
*PMD Thread Core Affinity*
pmd thread numa_id 1 core_id 17:
isolated : false
port: dpdk0 queue-id: 0
port: vhu43378b38-cb queue-id: 0
port: vhu8d094814-25 queue-id: 0
*Case I: When receiver application on VM is using numa_id 0 and pmd_thread
is using numa_id 1*
Packet is going from vhost to VM via QPI
Intel(r) QPI traffic estimation in bytes (data and non-data traffic
outgoing from CPU/socket through QPI links):
QPI0 QPI1
---------------------------------------------------------------------------------------------------------------
SKT 0 3% 4%
SKT 1 3% 3%
In this case, no packet is dropped at vhost level.
*Case II: When my receiver application is using numa_id 1 and pmd_thread is
using numa_id 1*
QPI monitoring
Intel(r) QPI traffic estimation in bytes (data and non-data traffic
outgoing from CPU/socket through QPI links):
QPI0 QPI1
---------------------------------------------------------------------------------------------------------------
SKT 0 0% 0%
SKT 1 0% 0%
In this case, I m facing continuous packet drop at vhost level.
Following things that I tried, but none of them worked
1. RX descriptors values (512, 1024, 2048, 4096)
2. MBUF_CACHE_SIZE values (128, 512)
Please suggest where I m doing wrong? Maybe I've missed something and
compute node is missing some configuration that is causing this issue.
Regards
Dheeraj Dang
reply other threads:[~2019-03-02 2:32 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=CAJyVW4-i6rhC1dVe+MSwejd8hCNwDNusC0pR7Op7CK+-mXOLfQ@mail.gmail.com \
--to=dheerajdang138@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).