From: Itai Sharoni <isharoni@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Maayan Kashani <mkashani@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>, Bing Zhao <bingz@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ophir Munk <ophirmu@nvidia.com>
Subject: Re: [PATCH] net/mlx5/windows: fix match criteria in flow creation
Date: Mon, 17 Nov 2025 09:10:59 +0000 [thread overview]
Message-ID: <SA1PR12MB8699670ECC88DA40004DF41EA1C9A@SA1PR12MB8699.namprd12.prod.outlook.com> (raw)
In-Reply-To: <11095513.IZOipudI63@thomas>
> Why adding only NVGRE?
We added NVGRE support in response to a specific client request.
Unfortunately, we don't have the capacity to test and validate other
tunnel types for this upcoming release. We're focusing our resources
on ensuring NVGRE works reliably.
We definitely see value in expanding tunnel support on Windows in
future releases. We can consider adding other tunnel types (VXLAN,
GRE, GENEVE, etc.) as a feature for a future release once we have
the resources to properly test and validate them.
> Should we mention which tunnels are supported on Windows in the doc?
Good suggestion, I've added documentation in v2 of the patch. The
documentation now lists NVGRE as supported and notes that it requires
DevX dynamic insertion mode. This makes it easy to expand the list
when we add more tunnel types in future releases.
prev parent reply other threads:[~2025-11-17 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 12:26 Itai Sharoni
2025-11-13 22:37 ` Thomas Monjalon
2025-11-17 8:45 ` [PATCH v2] " Itai Sharoni
2025-11-17 9:10 ` Itai Sharoni [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=SA1PR12MB8699670ECC88DA40004DF41EA1C9A@SA1PR12MB8699.namprd12.prod.outlook.com \
--to=isharoni@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=ophirmu@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).