Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Patch v4 00/18] Enable Intel VF flow director with DDP
Date: Fri, 19 Feb 2021 13:13:19 -0800	[thread overview]
Message-ID: <20210219131319.00000079@intel.com> (raw)
In-Reply-To: <20210219130001.49600-1-haiyue.wang@intel.com>

Haiyue Wang wrote:

> The Intel E810 Series supports a programmable pipeline for a domain
> specific protocols classification, for example GTP by Dynamic Device
> Personalization (DDP) profile.
> 
> The E810 PF has introduced flex-bytes support by ethtool user-def option
> allowing for packet deeper matching based on an offset and value for DDP
> usage.
> 
> For making VF also benefit from this flexible protocol classification, some
> new virtchnl messages are defined and handled by PF, so VF can query this
> new flow director capability, and use ethtool with extending the user-def
> option to configure Rx flow classification.
> 
> The new user-def 0xAAAABBBBCCCCDDDD: BBBB is the 2 byte pattern while AAAA
> corresponds to its offset in the packet. Similarly DDDD is the 2 byte
> pattern with CCCC being the corresponding offset. The offset ranges from
> 0x0 to 0x1F7 (up to 504 bytes into the packet). The offset starts from
> the beginning of the packet.

Why must you use the ethtool user-def interface like this? I suspect
that you should be using tc-u32.

At the very least you should cover why you're *not* using u32 in the
cover letter, otherwise I'm sure the question will come up.

 
> This feature can be used to allow customers to set flow director rules
> for protocols headers that are beyond standard ones supported by ethtool
> (e.g. PFCP or GTP-U).
> 
> Like for matching GTP-U's TEID value 0x10203040:
> ethtool -N ens787f0v0 flow-type udp4 dst-port 2152 \
>



      parent reply	other threads:[~2021-02-19 21:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 12:59 [Intel-wired-lan] [Patch v4 00/18] Enable Intel VF flow director with DDP Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 01/18] ice: Add more basic protocol support for flow filter Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 02/18] ice: Support non word aligned input set field Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 03/18] ice: Add more advanced protocol support in flow filter Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 04/18] ice: Support to separate GTP-U uplink and downlink Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 05/18] ice: Enhanced IPv4 and IPv6 flow filter Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 06/18] ice: Add support for per VF ctrl VSI enabling Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 07/18] ice: Enable FDIR Configure for AVF Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 08/18] ice: Add FDIR pattern action parser for VF Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 09/18] ice: Add new actions support for VF FDIR Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 10/18] ice: Add non-IP Layer2 protocol FDIR filter for AVF Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 11/18] ice: Add GTPU " Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 12/18] ice: Add more FDIR filter type " Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 13/18] ice: Check FDIR program status " Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 14/18] iavf: Add framework to enable ethtool ntuple filters Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 15/18] iavf: Support IPv4 Flow Director filters Haiyue Wang
2021-02-19 12:59 ` [Intel-wired-lan] [Patch v4 16/18] iavf: Support IPv6 " Haiyue Wang
2021-02-19 13:00 ` [Intel-wired-lan] [Patch v4 17/18] iavf: Support Ethernet Type " Haiyue Wang
2021-02-19 13:00 ` [Intel-wired-lan] [Patch v4 18/18] iavf: Enable flex-bytes support Haiyue Wang
2021-02-19 21:13 ` Jesse Brandeburg [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=20210219131319.00000079@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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