From: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>
To: "Xu, Ke1" <ke1.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/iavf: fix Tunnel TSO path selecting.
Date: Thu, 6 Jul 2023 06:07:53 +0000 [thread overview]
Message-ID: <SJ0PR11MB561331E82F52B916A371312EF12CA@SJ0PR11MB5613.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230706024526.1017993-1-ke1.xu@intel.com>
> -----Original Message-----
> From: Xu, Ke1 <ke1.xu@intel.com>
> Sent: Thursday, July 6, 2023 10:45 AM
> To: dev@dpdk.org
> Cc: Xu, Ke1 <ke1.xu@intel.com>; Zeng, ZhichaoX
> <zhichaox.zeng@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>;
> stable@dpdk.org
> Subject: [PATCH v2] net/iavf: fix Tunnel TSO path selecting.
>
> IAVF currently supports TSO and Tunnel TSO. Both these two features are
> implemented in scalar path. As there are missed flags for Tunnel TSO, it
> selects vector paths wrongly when only Tunnel TSO is enabled after
> introducing the patch "net/iavf: add offload path for Tx AVX512".
>
> This patch added the missed flags to fix the Tunnel TSO path selecting.
>
> Fixes: 059f18ae2aec ("net/iavf: add offload path for Tx AVX512")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ke Xu <ke1.xu@intel.com>
> ---
> v2: Add fixline, add CC, fix commit message.
> ---
Acked-by: Zhichao Zeng <zhichaox.zeng@intel.com>
next prev parent reply other threads:[~2023-07-06 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 10:35 [PATCH] " Ke Xu
2023-07-06 2:45 ` [PATCH v2] " Ke Xu
2023-07-06 6:07 ` Zeng, ZhichaoX [this message]
2023-07-06 6:29 ` Zhang, Qi Z
2023-07-06 2:34 Ke 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=SJ0PR11MB561331E82F52B916A371312EF12CA@SJ0PR11MB5613.namprd11.prod.outlook.com \
--to=zhichaox.zeng@intel.com \
--cc=dev@dpdk.org \
--cc=ke1.xu@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).