From: Bruce Richardson <bruce.richardson@intel.com>
To: Shaiq Wani <shaiq.wani@intel.com>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>
Subject: Re: [PATCH] net/cpfl: enable AVX2 for singleq Rx/Tx
Date: Tue, 8 Apr 2025 17:16:11 +0100 [thread overview]
Message-ID: <Z_VLy_b-7Ld4yidR@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250312155242.409854-1-shaiq.wani@intel.com>
On Wed, Mar 12, 2025 at 09:22:42PM +0530, Shaiq Wani wrote:
> In case some CPUs don't support AVX512. Enable AVX2 for them to
> get better per-core performance.
>
> The single queue model processes all packets in order while
> the split queue model separates packet data and metadata into
> different queues for parallel processing and improved performance.
>
> Signed-off-by: Shaiq Wani <shaiq.wani@intel.com>
> ---
> doc/guides/nics/cpfl.rst | 3 ++-
> drivers/net/intel/cpfl/cpfl_rxtx.c | 24 ++++++++++++++++++++++++
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst
> index 154201e745..5d267ef667 100644
> --- a/doc/guides/nics/cpfl.rst
> +++ b/doc/guides/nics/cpfl.rst
> @@ -177,7 +177,8 @@ The paths are chosen based on 2 conditions:
>
> On the x86 platform, the driver checks if the CPU supports AVX512.
> If the CPU supports AVX512 and EAL argument ``--force-max-simd-bitwidth``
> - is set to 512, AVX512 paths will be chosen.
> + is set to 512, AVX512 paths will be chosen. Otherwise, if --force-max-simd-bitwidth is set to 256,AVX2 paths will be chosen.
> + (Note that 256 is the default bitwidth if no specific value is provided.)
>
The word wrapping and spacing here looks wrong. Will fix on apply.
Otherwise
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2025-04-08 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 15:52 Shaiq Wani
2025-04-08 16:16 ` Bruce Richardson [this message]
2025-04-08 16:17 ` Bruce Richardson
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=Z_VLy_b-7Ld4yidR@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=shaiq.wani@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).