From: Thomas Monjalon <thomas@monjalon.net>
To: qi.z.zhang@intel.com, Ting Xu <ting.xu@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com, junfeng.guo@intel.com,
orika@nvidia.com, viacheslavo@nvidia.com, ferruh.yigit@intel.com,
andrew.rybchenko@oktetlabs.ru
Subject: Re: [dpdk-dev] [PATCH v4 0/2] enable protocol agnostic flow offloading in RSS
Date: Fri, 05 Nov 2021 14:09:43 +0100 [thread overview]
Message-ID: <2404603.ePvfOphbkP@thomas> (raw)
In-Reply-To: <20211104022228.46086-1-ting.xu@intel.com>
04/11/2021 03:22, Ting Xu:
> Enable protocol agnostic flow offloading to support raw pattern input
> for RSS hash flow rule creation. It is based on Parser Library feature.
> Current rte_flow raw API is utilized.
I remember raw item was especially targetting encapsulation action.
Which action do you achieve in ice PMD? Only RSS with raw item?
For matching, raw item is quite limited. I think the new flex item
is more appropriate for general custom protocol parsing.
Did you look into flex item feature?
next prev parent reply other threads:[~2021-11-05 13:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 7:09 [dpdk-dev] [PATCH v1 " Ting Xu
2021-10-08 7:09 ` [dpdk-dev] [PATCH v1 1/2] net/ice: " Ting Xu
2021-10-08 7:09 ` [dpdk-dev] [PATCH v1 2/2] doc: add protocol agnostic flow offloading for RSS hash Ting Xu
2021-11-01 11:02 ` [dpdk-dev] [PATCH v2 0/3] enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-01 11:02 ` [dpdk-dev] [PATCH v2 1/3] net/ice: " Ting Xu
2021-11-01 11:02 ` [dpdk-dev] [PATCH v2 2/3] " Ting Xu
2021-11-01 11:02 ` [dpdk-dev] [PATCH v2 3/3] doc: add protocol agnostic flow offloading for RSS Ting Xu
2021-11-01 11:05 ` [dpdk-dev] [PATCH v2 0/3] enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-01 11:05 ` [dpdk-dev] [PATCH v2 1/3] net/ice/base: support add HW profile for RSS raw flow Ting Xu
2021-11-01 11:05 ` [dpdk-dev] [PATCH v2 2/3] net/ice: enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-01 11:05 ` [dpdk-dev] [PATCH v2 3/3] doc: add protocol agnostic flow offloading for RSS Ting Xu
2021-11-02 1:49 ` [dpdk-dev] [PATCH v3 0/3] enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-02 1:49 ` [dpdk-dev] [PATCH v3 1/3] net/ice/base: support add HW profile for RSS raw flow Ting Xu
2021-11-02 1:49 ` [dpdk-dev] [PATCH v3 2/3] net/ice: enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-03 14:13 ` Ferruh Yigit
2021-11-04 3:29 ` Xu, Ting
2021-11-02 1:49 ` [dpdk-dev] [PATCH v3 3/3] doc: add protocol agnostic flow offloading for RSS Ting Xu
2021-11-03 12:45 ` [dpdk-dev] [PATCH v3 0/3] enable protocol agnostic flow offloading in RSS Zhang, Qi Z
2021-11-03 14:15 ` Ferruh Yigit
2021-11-04 2:22 ` [dpdk-dev] [PATCH v4 0/2] " Ting Xu
2021-11-04 2:22 ` [dpdk-dev] [PATCH v4 1/2] net/ice/base: support add HW profile for RSS raw flow Ting Xu
2021-11-04 2:22 ` [dpdk-dev] [PATCH v4 2/2] net/ice: enable protocol agnostic flow offloading in RSS Ting Xu
2021-11-04 3:31 ` [dpdk-dev] [PATCH v4 0/2] " Zhang, Qi Z
2021-11-05 13:09 ` Thomas Monjalon [this message]
2021-11-05 13:18 ` Xu, Ting
2021-11-05 13:23 ` Thomas Monjalon
2021-11-05 14:53 ` Xu, Ting
2021-11-08 2:44 ` Zhang, Qi Z
2021-11-08 19:47 ` Thomas Monjalon
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=2404603.ePvfOphbkP@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=junfeng.guo@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=ting.xu@intel.com \
--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).