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>,
"Chu, Haijun" <haijun.chu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
"Zhou, YidingX" <yidingx.zhou@intel.com>
Subject: RE: [PATCH] net/iavf: fix avx512 Tx path
Date: Thu, 23 Feb 2023 08:17:27 +0000 [thread overview]
Message-ID: <PH7PR11MB60569F1E5E77E4694C311C15D3AB9@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230222081311.74488-1-zhichaox.zeng@intel.com>
> -----Original Message-----
> From: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Sent: Wednesday, February 22, 2023 4:13 PM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Xu, Ke1 <ke1.xu@intel.com>; Chu,
> Haijun <haijun.chu@intel.com>; Zeng, ZhichaoX <zhichaox.zeng@intel.com>;
> Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Richardson, Bruce <bruce.richardson@intel.com>; Konstantin Ananyev
> <konstantin.v.ananyev@yandex.ru>; Zhou, YidingX <yidingx.zhou@intel.com>
> Subject: [PATCH] net/iavf: fix avx512 Tx path
>
> This patch fixes the tunneling parameters on avx512 Tx path and adjusts the
> path selection to fix perf drop.
>
> Fixes: 4f8259df563a ("net/iavf: enable Tx outer checksum offload on
> AVX512")
>
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>
Validated function and perf, passed.
Tested-by: Ke Xu <ke1.xu@intel.com>
> ---
> drivers/net/iavf/iavf_rxtx.c | 7 +--
> drivers/net/iavf/iavf_rxtx.h | 5 +-
> drivers/net/iavf/iavf_rxtx_vec_avx512.c | 82 ++++++++++++++++++++++---
> drivers/net/iavf/iavf_rxtx_vec_common.h | 23 +++----
> 4 files changed, 87 insertions(+), 30 deletions(-)
>
next prev parent reply other threads:[~2023-02-23 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 8:13 Zhichao Zeng
2023-02-23 8:17 ` Xu, Ke1 [this message]
2023-02-24 2:45 ` 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=PH7PR11MB60569F1E5E77E4694C311C15D3AB9@PH7PR11MB6056.namprd11.prod.outlook.com \
--to=ke1.xu@intel.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=haijun.chu@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=qi.z.zhang@intel.com \
--cc=yidingx.zhou@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).