From: Stephen Hemminger <stephen@networkplumber.org>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: 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>, <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [PATCH] net/mlx5: document IP fragment matching limitations
Date: Fri, 18 Jul 2025 08:18:35 -0700 [thread overview]
Message-ID: <20250718081835.15134b8c@hermes.local> (raw)
In-Reply-To: <20250718115156.1220403-1-dsosnowski@nvidia.com>
On Fri, 18 Jul 2025 13:51:56 +0200
Dariusz Sosnowski <dsosnowski@nvidia.com> wrote:
> NVIDIA NICs do not support matching on packet headers appearing
> after IP header if the received packet is an IP fragment.
> This patch updates the relevant documentation.
>
> Bugzilla ID: 1417
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
I suspect that is true of all NIC's because matching later fragments
would require state that would not scale in HW.
prev parent reply other threads:[~2025-07-18 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 11:51 Dariusz Sosnowski
2025-07-18 15:18 ` 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=20250718081835.15134b8c@hermes.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--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).