All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, "Dariusz Sosnowski" <dsosnowski@nvidia.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	"Bing Zhao" <bingz@nvidia.com>, "Ori Kam" <orika@nvidia.com>,
	"Suanming Mou" <suanmingm@nvidia.com>,
	"Matan Azrad" <matan@nvidia.com>
Subject: Re: [PATCH dpdk] net/mlx5: add option to reduce Tx datapath compilation time
Date: Tue, 28 Apr 2026 17:59:32 +0200	[thread overview]
Message-ID: <DI4WVC4VQYG9.7AI1V4UPUGY2@redhat.com> (raw)
In-Reply-To: <aeh4a5HS9iFtm9_D@bricha3-mobl1.ger.corp.intel.com>

Bruce Richardson, Apr 22, 2026 at 09:27:
> Out of interest, do you have any numbers for the performance delta between
> the release builds with and without the new flag? I'm just wondering if the
> flag can be the default to speed up builds generally?

The raw performance will depend on which offload features are enabled.
I have tested with the hardware I have at hand and these 3 TX offload
combinations:

0x10000: FAST_FREE
0x10020: FAST_FREE TCP_TSO
0x1008f: FAST_FREE TCP_TSO UDP_TSO UDP_CKSUM TCP_CKSUM IPV4_CKSUM VLAN_INSERT

MINIMAL_TX   TX_OFFLOADS    TX_FUNC                      NON_DROP_RATE
============ ============== ============================ ==============
off          0x10000        mlx5_tx_burst_none_empw      42.4M
off          0x10020        mlx5_tx_burst_mt_empw        39.4M
off          0x1008f        mlx5_tx_burst_sciv_empw      30.2M
on           0x10000        mlx5_tx_burst_full_noi_empw  36.2M
on           0x10020        mlx5_tx_burst_full_noi_empw  36.2M
on           0x1008f        mlx5_tx_burst_full_empw      30.2M

There is obviously something wrong with my patch. I need to make sure
the *no offload* case does not result in -15% of performance.

> [Not that it should affect me that much, I generally use
> -Denable_drivers flag when configuring my builds to only select the
> specific drivers I want]

I usually do this too but it turns out I *always* need mlx5 ;)


      reply	other threads:[~2026-04-28 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 21:23 [PATCH dpdk] net/mlx5: add option to reduce Tx datapath compilation time Robin Jarry
2026-04-21 21:56 ` Stephen Hemminger
2026-04-22  7:27 ` Bruce Richardson
2026-04-28 15:59   ` Robin Jarry [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=DI4WVC4VQYG9.7AI1V4UPUGY2@redhat.com \
    --to=rjarry@redhat.com \
    --cc=bingz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    /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.