From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: RE: [PATCH 2/2] common/idpf: enable AVX2 for single queue Tx
Date: Tue, 9 Jan 2024 09:55:24 +0000 [thread overview]
Message-ID: <BN0PR11MB57123B4D6F15D601516558F5FD6A2@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231207063514.2001192-3-wenzhuo.lu@intel.com>
> -----Original Message-----
> From: Wenzhuo Lu <wenzhuo.lu@intel.com>
> Sent: Thursday, December 7, 2023 2:35 PM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: [PATCH 2/2] common/idpf: enable AVX2 for single queue Tx
>
> In case some CPUs don't support AVX512. Enable AVX2 for them to get better
> per-core performance.
>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
Verified idpf single queue + AVX2 in functional regression test, tested pass.
Tested-by: Zhimin Huang <zhiminx.huang@intel.com >
next prev parent reply other threads:[~2024-01-09 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 6:35 [PATCH 0/2] enable AVX2 for IDPF single queue Wenzhuo Lu
2023-12-07 6:35 ` [PATCH 1/2] common/idpf: enable AVX2 for single queue Rx Wenzhuo Lu
2023-12-07 6:35 ` [PATCH 2/2] common/idpf: enable AVX2 for single queue Tx Wenzhuo Lu
2024-01-09 9:55 ` Huang, ZhiminX [this message]
2023-12-07 7:46 ` [PATCH v2 0/2] enable AVX2 for IDPF single queue Wenzhuo Lu
2023-12-07 7:46 ` [PATCH v2 1/2] common/idpf: enable AVX2 for single queue Rx Wenzhuo Lu
2023-12-07 7:46 ` [PATCH v2 2/2] common/idpf: enable AVX2 for single queue Tx Wenzhuo Lu
2025-01-08 12:17 [PATCH 0/2] enable AVX2 for IDPF single queue Shaiq Wani
2025-01-08 12:17 ` [PATCH 2/2] common/idpf: enable AVX2 for single queue Tx Shaiq Wani
2025-01-20 14:23 ` Bruce Richardson
2025-01-27 9:46 ` Wani, Shaiq
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=BN0PR11MB57123B4D6F15D601516558F5FD6A2@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@intel.com \
--cc=dev@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).