From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Junfeng Guo <junfeng.guo@intel.com>, <intel-wired-lan@lists.osuosl.org>
Cc: qi.z.zhang@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 0/3] Enable the raw flow filtering for FDIR
Date: Thu, 24 Aug 2023 13:44:30 -0700 [thread overview]
Message-ID: <9e3378aa-625a-b5c7-995e-75f532a16102@intel.com> (raw)
In-Reply-To: <20230605024453.2378898-1-junfeng.guo@intel.com>
On 6/4/2023 7:44 PM, Junfeng Guo wrote:
> This patch set provides a method for applications to send down
> training packets & masks (in binary) to the driver to do Flow
> Director (FDIR) filtering. Based on the Parser Library, these
> binary data would be used by the driver to figure out the infomations
> that are needed to create/destroy the FDIR rule in the FDIR stage.
>
> With this patch set, the raw flow filtering for FDIR could be enabled
> to allow new flow offloading features to be supported without any
> driver changes (only need to update the Dynamic Device
> Personalization package).
Please do not send patches that are dependent on other code until they
dependencies have been applied. Otherwise these can not be checked
properly [1].
> Junfeng Guo (3):
> virtchnl: support raw packet in protocol header
> ice: add method to disable FDIR SWAP option
> ice: enable Protocol Agnostic Flow Offloading FDIR
>
> .../net/ethernet/intel/ice/ice_flex_pipe.c | 98 +++-
> .../net/ethernet/intel/ice/ice_flex_pipe.h | 5 +-
> drivers/net/ethernet/intel/ice/ice_flow.c | 109 ++++-
> drivers/net/ethernet/intel/ice/ice_flow.h | 5 +
> drivers/net/ethernet/intel/ice/ice_vf_lib.h | 8 +
> .../ethernet/intel/ice/ice_virtchnl_fdir.c | 448 +++++++++++++++++-
> include/linux/avf/virtchnl.h | 12 +-
> 7 files changed, 678 insertions(+), 7 deletions(-)
[1]
https://lore.kernel.org/intel-wired-lan/202308232207.mbURs2VO-lkp@intel.com/
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-08-24 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 2:44 [Intel-wired-lan] [PATCH iwl-next 0/3] Enable the raw flow filtering for FDIR Junfeng Guo
2023-06-05 2:44 ` [Intel-wired-lan] [PATCH iwl-next 1/3] virtchnl: support raw packet in protocol header Junfeng Guo
2023-06-05 2:44 ` [Intel-wired-lan] [PATCH iwl-next 2/3] ice: add method to disable FDIR SWAP option Junfeng Guo
2023-06-05 2:44 ` [Intel-wired-lan] [PATCH iwl-next 3/3] ice: enable Protocol Agnostic Flow Offloading FDIR Junfeng Guo
2023-06-05 5:18 ` kernel test robot
2023-06-05 11:30 ` kernel test robot
2023-08-18 6:47 ` [Intel-wired-lan] [PATCH iwl-next v2 0/3] Enable the raw flow filtering for FDIR Junfeng Guo
2023-08-18 6:47 ` [Intel-wired-lan] [PATCH iwl-next v2 1/3] virtchnl: support raw packet in protocol header Junfeng Guo
2023-08-18 6:47 ` [Intel-wired-lan] [PATCH iwl-next v2 2/3] ice: add method to disable FDIR SWAP option Junfeng Guo
2023-08-18 6:47 ` [Intel-wired-lan] [PATCH iwl-next v2 3/3] ice: enable Protocol Agnostic Flow Offloading FDIR Junfeng Guo
2023-08-22 15:20 ` kernel test robot
2023-08-23 14:25 ` kernel test robot
2023-08-24 20:44 ` Tony Nguyen [this message]
2023-08-28 6:57 ` [Intel-wired-lan] [PATCH iwl-next 0/3] Enable the raw flow filtering for FDIR Guo, Junfeng
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=9e3378aa-625a-b5c7-995e-75f532a16102@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@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