From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Malov <ivan.malov@arknetworks.am>
Cc: "Lombardo, Ed" <Ed.Lombardo@netscout.com>, users <users@dpdk.org>
Subject: Re: dpdk Tx falling short
Date: Fri, 4 Jul 2025 07:49:57 -0700 [thread overview]
Message-ID: <20250704074957.5848175a@hermes.local> (raw)
In-Reply-To: <e539b223-d2fb-447f-4117-fc89fe7ee318@arknetworks.am>
On Fri, 4 Jul 2025 15:44:50 +0400 (+04)
Ivan Malov <ivan.malov@arknetworks.am> wrote:
> Hi Ed,
>
> You say there is only one mempool. Why?
> Have you tried using dedicated mempools, one per each port pair (0,2), (3,4)?
>
> Thank you.
>
> On Thu, 3 Jul 2025, Lombardo, Ed wrote:
More mempools can make cache behavior worse not better.
prev parent reply other threads:[~2025-07-04 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 20:14 Lombardo, Ed
2025-07-03 21:49 ` Stephen Hemminger
2025-07-04 5:58 ` Rajesh Kumar
2025-07-04 11:44 ` Ivan Malov
2025-07-04 14:49 ` Stephen Hemminger [this message]
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=20250704074957.5848175a@hermes.local \
--to=stephen@networkplumber.org \
--cc=Ed.Lombardo@netscout.com \
--cc=ivan.malov@arknetworks.am \
--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).