DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Ding, Xuan" <xuan.ding@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Wang, Haiyue" <haiyue.wang@intel.com>,
	"Guo, Jia" <jia.guo@intel.com>, "Su, Simei" <simei.su@intel.com>,
	"Yan, Zhirun" <zhirun.yan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ice: refactor PF RSS
Date: Mon, 11 Jan 2021 03:17:05 +0000	[thread overview]
Message-ID: <7a63e3a845ef4b5c8339068abaa7a9e1@intel.com> (raw)
In-Reply-To: <20210108083844.72065-1-xuan.ding@intel.com>



> -----Original Message-----
> From: Ding, Xuan <xuan.ding@intel.com>
> Sent: Friday, January 8, 2021 4:39 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Wang, Haiyue <haiyue.wang@intel.com>; Guo, Jia
> <jia.guo@intel.com>; Su, Simei <simei.su@intel.com>; Yan, Zhirun
> <zhirun.yan@intel.com>; Ding, Xuan <xuan.ding@intel.com>
> Subject: [PATCH] net/ice: refactor PF RSS
> 
> This patch refactors the PF RSS code based on the below design:
> 1. ice_pattern_match_item->input_set_mask is the superset of
>    ETH_RSS_xxx.
> 2. ice_pattern_match_item->meta is the ice_rss_hash_cfg template.
> 3. ice_hash_parse_pattern will generate pattern hint.
> 4. ice_hash_parse_action will refine the ice_rss_hash_cfg based on
>    the pattern hint and rss_type.
> 5. The refine process includes:
>    1)  refine protocol headers(VLAN/PPPOE/GTPU).
>    2)  refine hash bit fields of l2, l3, l4.
>    3)  refine hash bit fields for gtpu header.
> 
> Signed-off-by: Xuan Ding <xuan.ding@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

      reply	other threads:[~2021-01-11  3:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08  8:38 Xuan Ding
2021-01-11  3:17 ` Zhang, Qi Z [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=7a63e3a845ef4b5c8339068abaa7a9e1@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=jia.guo@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=simei.su@intel.com \
    --cc=xuan.ding@intel.com \
    --cc=zhirun.yan@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).