From: "Minggang(Gavin) Li" <gavinl@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Bing Zhao <bingz@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Maayan Kashani <mkashani@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix IPv6 DSCP offset in NT HWS API
Date: Wed, 12 Nov 2025 12:47:26 +0000 [thread overview]
Message-ID: <IA0PR12MB8376E03456B1B6D738F70FC1B3CCA@IA0PR12MB8376.namprd12.prod.outlook.com> (raw)
In-Reply-To: <4447141.2yuIWEeYC1@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, November 12, 2025 5:10 PM
> To: Minggang(Gavin) Li <gavinl@nvidia.com>; Bing Zhao <bingz@nvidia.com>
> Cc: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Dariusz Sosnowski
> <dsosnowski@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>;
> dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; stable@dpdk.org;
> Maayan Kashani <mkashani@nvidia.com>
> Subject: Re: [PATCH] net/mlx5: fix IPv6 DSCP offset in NT HWS API
>
> 12/11/2025 09:58, Bing Zhao:
> > Maybe the title can be changed to non-template API directly instead of NT
> HWS?
>
> No, the correct name is synchronous flow API with hardware steering.
> You can shorten it as "HWS sync API".
ACK
>
>
next prev parent reply other threads:[~2025-11-12 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 7:28 Gavin Li
2025-11-12 8:58 ` Bing Zhao
2025-11-12 9:09 ` Thomas Monjalon
2025-11-12 12:47 ` Minggang(Gavin) Li [this message]
2025-11-12 13:01 ` [PATCH V2] net/mlx5: fix IPv6 DSCP offset in HWS sync API Gavin Li
2025-11-12 13:42 ` [PATCH V3] " Gavin Li
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=IA0PR12MB8376E03456B1B6D738F70FC1B3CCA@IA0PR12MB8376.namprd12.prod.outlook.com \
--to=gavinl@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--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 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).