DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yaron Illouz <yaroni@radcom.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: rxq_cq_process_v high cpu
Date: Wed, 9 Feb 2022 18:24:17 +0000	[thread overview]
Message-ID: <AM9PR09MB499504A2D38A274E7FA1DE81A12E9@AM9PR09MB4995.eurprd09.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]


I moved from dpdk 19 to dpdk 21
I read with multiqueue from Mellanox 100G card with dpdk function rte_eth_rx_burst
I can see in perf top very high cpu on function rxq_cq_process_v
How can i fix it? This function wasn't in my perf top with dpdk 19 version
53.12%  libdpdkutils.so               [.] rxq_cq_process_v
16.25%  libdpdkutils.so               [.] mlx5_rx_burst_vec
  5.50%  libcaptureimpl.so             [.] CrPacketReceiver::ReadFromPort
  2.06%  libdpdkutils.so               [.] CrDpdkDeviceUtil::GetPacketDetails
  2.04%  libhpadecoders.so             [.] CrReorderMbuf::GetTimedOut
  1.55%  libhpahwswmsg.so              [.] CrNetworkPacket::FindEthernetTypeAndPayload
  1.25%  libcaptureimpl.so             [.] CrPacketReceiver::FullPollMode
  1.17%  libdpdkutils.so               [.] rte_eth_dev_is_valid_port
  0.96%  libhpartpdecoderimpl.so       [.] CrRtpProcessing::GetSession
  0.77%  libdpdkutils.so               [.] CrDpdkDeviceUtil::InitPacketDetailsFromBuff
  0.66%  libhpartpdecoderimpl.so       [.] VQmonStreamIndicatePacket
  0.63%  libhpartpdecoderimpl.so       [.] VQmonJitterBufferIndicatePacket


[-- Attachment #2: Type: text/html, Size: 7802 bytes --]

                 reply	other threads:[~2022-02-09 18:24 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=AM9PR09MB499504A2D38A274E7FA1DE81A12E9@AM9PR09MB4995.eurprd09.prod.outlook.com \
    --to=yaroni@radcom.com \
    --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).