DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: cache miss increases when change rx descriptor from 512 to 2048
Date: Thu, 9 Feb 2023 03:58:56 +0000	[thread overview]
Message-ID: <4b132ffd05594663b5abb71f42e6f97f@nokia-sbell.com> (raw)

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

Hi experts,

I had a traffic throughput test for my dpdk application, with same software and test case, only difference is the number of rx/tx descriptor:
Rx/tx descriptor 512, test result 3.2mpps
Rx/tx descriptor 2048, test result 3mpp
From perf data, rx descriptor 2048 case has more cache miss, and lower instruction per cycle
Perf for 512 rx descriptor
      114289237792      cpu-cycles
      365408402395      instructions              #    3.20  insn per cycle
       74186289932      branches
          36020793      branch-misses             #    0.05% of all branches
        1298741388      bus-cycles
           3413460      cache-misses              #    0.723 % of all cache refs
         472363654      cache-references
Perf for 2048 rx descriptor:
       57038451185      cpu-cycles
      173805485573      instructions              #    3.05  insn per cycle
       35289607389      branches
          15418885      branch-misses             #    0.04% of all branches
         648164239      bus-cycles
          13170596      cache-misses              #    1.702 % of all cache refs
         773765263      cache-references

I understand it means more rx descriptor somehow causes more cache miss and then less instruction per cycle, so lower performance.

Any one observe similar results?
Any idea to mitigate (or investigate further) the impact? (we want to use 2048 to better tolerate some jitter/burst)
Any comment?

Thank you.

Br, Xiaoping


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

             reply	other threads:[~2023-02-09  3:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  3:58 Xiaoping Yan (NSB) [this message]
2023-02-09 16:38 ` Stephen Hemminger
2023-02-10  1:59   ` Xiaoping Yan (NSB)
2023-02-10  2:38     ` Stephen Hemminger
2023-02-10  2:50       ` Xiaoping Yan (NSB)

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=4b132ffd05594663b5abb71f42e6f97f@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.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).