From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix L2 payload RSS mask input set
Date: Mon, 21 Jun 2021 08:39:17 +0000 [thread overview]
Message-ID: <MN2PR11MB3807D5BA6D8EA5DA120E3046F70A9@MN2PR11MB3807.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210618083821.9876-1-alvinx.zhang@intel.com>
> -----Original Message-----
> From: Zhang, AlvinX <alvinx.zhang@intel.com>
> Sent: Friday, June 18, 2021 4:38 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Zhang, AlvinX <alvinx.zhang@intel.com>;
> stable@dpdk.org
> Subject: [PATCH] net/i40e: fix L2 payload RSS mask input set
>
> Allow VLAN tag being added to L2 payload packet type RSS input set.
>
> Fixes: ef4c16fd9148 ("net/i40e: refactor RSS flow")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> ---
> drivers/net/i40e/i40e_hash.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/i40e/i40e_hash.c b/drivers/net/i40e/i40e_hash.c
> index b1cb24f..722edc9 100644
> --- a/drivers/net/i40e/i40e_hash.c
> +++ b/drivers/net/i40e/i40e_hash.c
> @@ -201,11 +201,11 @@ struct i40e_hash_match_pattern { #define
> I40E_HASH_MAP_CUS_PATTERN(pattern, rss_mask, cus_pctype) { \
> pattern, rss_mask, true, cus_pctype }
>
> -#define I40E_HASH_L2_RSS_MASK (ETH_RSS_ETH |
> ETH_RSS_L2_SRC_ONLY | \
> +#define I40E_HASH_L2_RSS_MASK (ETH_RSS_VLAN |
> ETH_RSS_ETH | \
> + ETH_RSS_L2_SRC_ONLY | \
> ETH_RSS_L2_DST_ONLY)
>
> #define I40E_HASH_L23_RSS_MASK (I40E_HASH_L2_RSS_MASK |
> \
> - ETH_RSS_VLAN | \
> ETH_RSS_L3_SRC_ONLY | \
> ETH_RSS_L3_DST_ONLY)
>
> --
> 1.8.3.1
Acked-by: Beilei Xing <beilei.xing@intel.com>
next prev parent reply other threads:[~2021-06-21 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 8:38 Alvin Zhang
2021-06-21 8:39 ` Xing, Beilei [this message]
2021-06-22 3:38 ` Zhang, Qi Z
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=MN2PR11MB3807D5BA6D8EA5DA120E3046F70A9@MN2PR11MB3807.namprd11.prod.outlook.com \
--to=beilei.xing@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).