From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Xu, Ting" <ting.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] net/ice: fix wrong IP RSS configuration template
Date: Mon, 10 May 2021 02:40:47 +0000 [thread overview]
Message-ID: <1de0dc11d0d44c01bf60f2f12ee0cd08@intel.com> (raw)
In-Reply-To: <20210508071147.4827-1-ting.xu@intel.com>
> -----Original Message-----
> From: Xu, Ting <ting.xu@intel.com>
> Sent: Saturday, May 8, 2021 3:12 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>; Xu, Ting <ting.xu@intel.com>; stable@dpdk.org
> Subject: [PATCH v1] net/ice: fix wrong IP RSS configuration template
>
> To enable IP fragment RSS hash, ICE_FLOW_SEG_HDR_IPV_FRAG is added to
> the IP RSS configuration template, together with
> ICE_FLOW_SEG_HDR_IPV_OTHER.
> It will cause error when associating flow profile. And packet id field for RSS is
> not correctly added when IP fragment is enabled. To fix this issue, this patch
> only selects one of the above two segment header types based on rss types.
>
> Fixes: 672f321d09ed ("net/ice: support RSS hash for IP fragment")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ting Xu <ting.xu@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2021-05-10 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 7:11 [dpdk-dev] [PATCH v1] net/ice: fix wrong IP RSS configuration template Ting Xu
2021-05-10 2:40 ` Zhang, Qi Z [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-07 9:52 Ting Xu
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=1de0dc11d0d44c01bf60f2f12ee0cd08@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=ting.xu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.