From: "Jiale, SongX" <songx.jiale@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ye, MingjinX" <mingjinx.ye@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: RE: [PATCH 3/3] net/ice: ACL filter support for IPv4 fragment
Date: Thu, 23 Jan 2025 09:35:03 +0000 [thread overview]
Message-ID: <BN0PR11MB5743C0AEED8AE33CAE96396DE7E02@BN0PR11MB5743.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250122082310.380054-4-mingjinx.ye@intel.com>
> -----Original Message-----
> From: Mingjin Ye <mingjinx.ye@intel.com>
> Sent: Wednesday, January 22, 2025 4:23 PM
> To: dev@dpdk.org
> Cc: Ye, MingjinX <mingjinx.ye@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Subject: [PATCH 3/3] net/ice: ACL filter support for IPv4 fragment
>
> Enable ACL filter on PF. Add support for FRAG_IPV4 pattern and queue action.
>
> Flow rule can be created by the following command:
> flow create 0 ingress group 1 pattern eth /
> ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x3FFF /
> end actions queue index <queue id> / end
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
Tested-by: Jiale Song <songx.jiale@intel.com>
next prev parent reply other threads:[~2025-01-23 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 8:23 [PATCH 0/3] flexible IPv4 fragment action Mingjin Ye
2025-01-22 8:23 ` [PATCH 1/3] net/ice/base: add ipv4 fragment related field Mingjin Ye
2025-01-22 8:23 ` [PATCH 2/3] net/ice: FDIR support IPv4 fragment masks Mingjin Ye
2025-01-22 8:23 ` [PATCH 3/3] net/ice: ACL filter support for IPv4 fragment Mingjin Ye
2025-01-23 9:35 ` Jiale, SongX [this message]
2025-01-22 11:23 ` [PATCH 0/3] flexible IPv4 fragment action Bruce Richardson
2025-01-23 8:52 ` Ye, MingjinX
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=BN0PR11MB5743C0AEED8AE33CAE96396DE7E02@BN0PR11MB5743.namprd11.prod.outlook.com \
--to=songx.jiale@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mingjinx.ye@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).