public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Jay Wang <jay.wang2@arm.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Anatoly Burakov <anatoly.burakov@intel.com>, <dev@dpdk.org>,
	<nd@arm.com>
Subject: Re: [PATCH v2] net/ice: add NEON-optimised Rx/Tx vector paths
Date: Tue, 7 Apr 2026 11:47:07 +0100	[thread overview]
Message-ID: <adTgq107Xrq4yLD0@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <ac_Pv0hhrBFlY5oy@bricha3-mobl1.ger.corp.intel.com>

On Fri, Apr 03, 2026 at 03:33:35PM +0100, Bruce Richardson wrote:
> On Tue, Mar 24, 2026 at 04:25:24PM +0000, Jay Wang wrote:
> > This patch adds the NEON-optimised Rx and Tx paths to the ice driver.
> > 
> > Tested on Ampere One platform with Intel E810-C NIC and 100G connection.
> > Tested with a single core and testpmd io forwarding mode. Observed
> > ~30% performance boost in the above test compared to the default scalar
> > path.
> > 
> > Signed-off-by: Jay Wang <jay.wang2@arm.com>
> > ---
> >  .mailmap                                  |   1 +
> >  drivers/net/intel/ice/ice_ethdev.h        |   3 +
> >  drivers/net/intel/ice/ice_rxtx.c          |  53 +-
> >  drivers/net/intel/ice/ice_rxtx.h          |   6 +
> >  drivers/net/intel/ice/ice_rxtx_vec_neon.c | 761 ++++++++++++++++++++++
> >  drivers/net/intel/ice/meson.build         |   2 +
> >  6 files changed, 824 insertions(+), 2 deletions(-)
> >  create mode 100644 drivers/net/intel/ice/ice_rxtx_vec_neon.c
> > 
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Applied to dpdk-next-net-intel
> 
Unfortunately, I've had to back this patch out again as it has caused
errors in the CI over the weekend e.g. [1]. No errors were reported with
the patch before I merged it, but I see now that not all tests were
successfully run on it. Can you please take a look at the CI errors
reported and submit a new version of this patch.

Thanks,
/Bruce


[1] https://lab.dpdk.org/results/dashboard/testruns/logs/1985291/

  reply	other threads:[~2026-04-07 10:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 18:32 [PATCH v1 0/1] net/ice: add Neon-optimised Rx/Tx vector paths Jay Wang
2026-03-23 18:32 ` [PATCH v1 1/1] " Jay Wang
2026-03-24 16:25   ` [PATCH v1 0/1] net/ice: add NEON-optimised " Jay Wang
2026-03-24 16:25     ` [PATCH v1 1/1] net/ice: add Neon-optimised " Jay Wang
2026-03-24 16:25     ` [PATCH v2] net/ice: add NEON-optimised " Jay Wang
2026-04-03 14:33       ` Bruce Richardson
2026-04-07 10:47         ` Bruce Richardson [this message]
2026-04-07 13:41           ` Jay Wang
2026-04-07 15:12       ` [PATCH v1 0/1] " Jay Wang
2026-04-07 15:12         ` [PATCH v1 1/1] net/ice: add Neon-optimised " Jay Wang
2026-04-07 15:12         ` [PATCH v2] net/ice: add NEON-optimised " Jay Wang
2026-04-07 15:12         ` [PATCH v3] " Jay Wang
2026-04-07 15:42           ` Jay Wang
2026-04-07 16:12             ` Bruce Richardson
2026-04-09 10:29               ` Jay Wang
2026-04-08 16:45           ` Bruce Richardson
2026-04-09 16:41           ` [PATCH v4 0/1] " Jay Wang
2026-04-09 16:41             ` [PATCH v4 1/1] " Jay Wang
2026-04-15 14:52               ` [PATCH v5] " Jay Wang
2026-04-16 13:04                 ` Bruce Richardson
2026-03-24 10:51 ` [PATCH v1 0/1] net/ice: add Neon-optimised " 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=adTgq107Xrq4yLD0@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jay.wang2@arm.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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