From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Zhichao Zeng <zhichaox.zeng@intel.com>, <dev@dpdk.org>,
<qi.z.zhang@intel.com>, Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Ian Stokes <ian.stokes@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH v3] net/iavf: support rte flow with mask for FDIR
Date: Tue, 21 Jan 2025 12:01:06 +0000 [thread overview]
Message-ID: <Z4-Mght_keEfrpZ4@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8ya119fpf_hYkq1r3aLtG8wO-W-E4+fiGwMRy-bGabBDw@mail.gmail.com>
On Thu, Aug 29, 2024 at 10:14:38AM +0200, David Marchand wrote:
> Hello,
>
> On Fri, Dec 15, 2023 at 4:19 AM Zhichao Zeng <zhichaox.zeng@intel.com>
> wrote:
> >
> > This patch supports rte flow with mask for FDIR, including
> > eth/ipv4/ipv6/tcp/udp flow items, where src/dst for ipv4/ipv6 and
> > sport/dport for tcp/udp are realized by switch filter.
> >
> > Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>
>
> Is this supposed to work with an upstream kernel? Is this patch supposed
> to get merged at some point in DPDK?
>
As I understand it, this patch is indeed blocked on lack of kernel support
to enable. Since the patch is >1yr old I'm going to mark it as "Not
Applicable" in patchwork rather than just marking it as "deferred" and
having it pop up again for 25.07 release. When all dependent support is
present, let's just submit a new version of the patch.
Regards,
/Bruce
prev parent reply other threads:[~2025-01-21 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 2:34 [PATCH] " Zhichao Zeng
2023-12-14 6:08 ` [PATCH v2] " Zhichao Zeng
2023-12-15 3:28 ` [PATCH v3] " Zhichao Zeng
2024-08-29 8:14 ` David Marchand
2025-01-21 12:01 ` Bruce Richardson [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=Z4-Mght_keEfrpZ4@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=zhichaox.zeng@intel.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).