From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Ciara Loftus <ciara.loftus@intel.com>, dev@dpdk.org
Subject: Re: [PATCH 3/4] net/ice: remove SSE vector path
Date: Tue, 26 Aug 2025 17:38:43 +0500 [thread overview]
Message-ID: <CA++2-x66ttTz6ZMSkPRgdfSo1dzzWR__T3Z1ETDGEiRZNusRQg@mail.gmail.com> (raw)
In-Reply-To: <aK2jBtI5qY4tnKEO@bricha3-mobl1.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Tue, Aug 26, 2025 at 5:05 PM Bruce Richardson <bruce.richardson@intel.com>
wrote:
>
> Yes, AXV2 and AVX-512 code paths have far higher performance than the
> scalar paths. However, that performance comes at the cost of not supporting
> all features. What the drivers then do at initialization time, is they
> check the offloads requested by the app, and then select the highest
> performance code path that can support those requested offloads.
> The whole process should be transparent to the user - they just get the
> best performance possible for their running conditions...
>
> /Bruce
>
Got it!
Thanks for the help.
Regards,
Khadem
[-- Attachment #2: Type: text/html, Size: 1101 bytes --]
next prev parent reply other threads:[~2025-08-26 12:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 12:35 [PATCH 0/4] Remove SSE from some Intel drivers Ciara Loftus
2025-08-25 12:35 ` [PATCH 1/4] net/i40e: remove SSE vector path Ciara Loftus
2025-08-25 12:35 ` [PATCH 2/4] net/iavf: " Ciara Loftus
2025-08-25 12:35 ` [PATCH 3/4] net/ice: " Ciara Loftus
2025-08-26 7:31 ` Khadem Ullah
2025-08-26 7:54 ` Bruce Richardson
2025-08-26 9:29 ` Khadem Ullah
2025-08-26 10:50 ` Bruce Richardson
2025-08-26 11:54 ` Khadem Ullah
2025-08-26 12:05 ` Bruce Richardson
2025-08-26 12:38 ` Khadem Ullah [this message]
2025-08-26 12:02 ` Khadem Ullah
2025-08-25 12:35 ` [PATCH 4/4] doc: add release note entry for SSE removal Ciara Loftus
2025-08-25 13:20 ` 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=CA++2-x66ttTz6ZMSkPRgdfSo1dzzWR__T3Z1ETDGEiRZNusRQg@mail.gmail.com \
--to=14pwcse1224@uetpeshawar.edu.pk \
--cc=bruce.richardson@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
/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).