From: "Xu, Ke1" <ke1.xu@intel.com>
To: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: RE: [PATCH] net/iavf: fix AVX2 path selection
Date: Thu, 6 Jul 2023 03:52:08 +0000 [thread overview]
Message-ID: <PH7PR11MB6056357220B3E0BF147083E2D32CA@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230706032023.1053203-1-zhichaox.zeng@intel.com>
> -----Original Message-----
> From: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Sent: Thursday, July 6, 2023 11:20 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Xu, Ke1 <ke1.xu@intel.com>;
> Zeng, ZhichaoX <zhichaox.zeng@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Lu,
> Wenzhuo <wenzhuo.lu@intel.com>
> Subject: [PATCH] net/iavf: fix AVX2 path selection
>
> The AVX2 path does not support outer checksum offload, when AVX2 is
> forcibly selected and outer checksum offload is configured, the basic Tx
> path will be selected to ensure proper functionality.
>
> Fixes: 5712bf9d6e14 ("net/iavf: add Tx AVX2 offload path")
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>
Verified path selection fixed.
Tested-by: Ke Xu <ke1.xu@intel.com>
> ---
> drivers/net/iavf/iavf_rxtx.c | 6 ++++++
> 1 file changed, 6 insertions(+)
> --
> 2.34.1
next prev parent reply other threads:[~2023-07-06 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 3:20 Zhichao Zeng
2023-07-06 3:52 ` Xu, Ke1 [this message]
2023-07-06 6:06 ` Zhang, Qi Z
-- strict thread matches above, loose matches on Subject: below --
2023-07-06 3:15 [PATCH] net/iavf: fix avx2 " Zhichao Zeng
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=PH7PR11MB6056357220B3E0BF147083E2D32CA@PH7PR11MB6056.namprd11.prod.outlook.com \
--to=ke1.xu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=zhichaox.zeng@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).