All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1148] Performance on AESNI MB PMD does not scale properly with number of threads
Date: Wed, 14 Dec 2022 10:58:00 +0000	[thread overview]
Message-ID: <bug-1148-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1148

            Bug ID: 1148
           Summary: Performance on AESNI MB PMD does not scale properly
                    with number of threads
           Product: DPDK
           Version: 22.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: pablo.de.lara.guarch@intel.com
  Target Milestone: ---

As number of threads is increased, performance per core on AESNI MB PMD
decreases (it should stay constant). The root cause of this issue is a global
variable in the IPSec Multi-buffer library. A patch has been generated to fix
it on the library, so users running the PMD with multiple threads are
encouraged to get the latest version (1.3.0) with the patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-12-14 10:58 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=bug-1148-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.