From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: Ivan Malov <ivan.malov@arknetworks.am>, users <users@dpdk.org>
Subject: Re: dpdk Tx falling short
Date: Sat, 5 Jul 2025 12:02:03 -0700 [thread overview]
Message-ID: <20250705120203.1d0c230c@hermes.local> (raw)
In-Reply-To: <CH3PR01MB84705581A7FED5E8F78C5F738F4DA@CH3PR01MB8470.prod.exchangelabs.com>
On Sat, 5 Jul 2025 17:36:08 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:
> Hi Stephen,
> I saw your response to more mempools and cache behavior.
>
> I have a goal to support 2x100G next, and if I can't get 10G with DPDK then something is seriously wrong.
>
> Should I build the dpdk static libraries with LTO?
>
> Thanks,
> Ed
>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, July 4, 2025 10:50 AM
> To: Ivan Malov <ivan.malov@arknetworks.am>
> Cc: Lombardo, Ed <Ed.Lombardo@netscout.com>; users <users@dpdk.org>
> Subject: Re: dpdk Tx falling short
>
> External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> 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.
Your best bet is to use tools like perf to profile cache misses.
next prev parent reply other threads:[~2025-07-05 19:02 UTC|newest]
Thread overview: 12+ 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
2025-07-05 17:36 ` Lombardo, Ed
2025-07-05 19:02 ` Stephen Hemminger [this message]
2025-07-05 19:08 ` Stephen Hemminger
2025-07-06 0:03 ` Lombardo, Ed
2025-07-06 16:02 ` Stephen Hemminger
2025-07-06 17:44 ` Lombardo, Ed
2025-07-05 17:33 ` Lombardo, Ed
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=20250705120203.1d0c230c@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).