From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Kathleen Capella <kathleen.capella@arm.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
Ruifeng Wang <ruifeng.wang@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"dharmik.thakkar@arm.com" <dharmik.thakkar@arm.com>
Subject: RE: [PATCH v4 1/1] net/iavf: add vector PMD for Arm for basic Rx path
Date: Sun, 19 Jun 2022 12:14:27 +0000 [thread overview]
Message-ID: <DM4PR11MB5994B3CAB8353551BA472E6DD7B19@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220617182134.15284-2-kathleen.capella@arm.com>
> -----Original Message-----
> From: Kathleen Capella <kathleen.capella@arm.com>
> Sent: Saturday, June 18, 2022 2:22 AM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Ruifeng Wang <ruifeng.wang@arm.com>
> Cc: dev@dpdk.org; nd@arm.com; honnappa.nagarahalli@arm.com;
> dharmik.thakkar@arm.com; Kathleen Capella <kathleen.capella@arm.com>
> Subject: [PATCH v4 1/1] net/iavf: add vector PMD for Arm for basic Rx path
>
> This patch adds the basic NEON Rx path to the iavf driver. It does not include
> scatter or flex varieties.
>
> Tested on N1SDP platform with Intel XL710 NIC and 40G connection.
> Tested with a single core and testpmd rxonly mode. Saw no significant
> performance difference between scalar and Arm vPMD paths using this test in
> iavf and saw the same results when comparing scalar and Arm vPMD path in
> i40e.
>
> Signed-off-by: Kathleen Capella <kathleen.capella@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-06-19 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 18:21 [PATCH v4 0/1] " Kathleen Capella
2022-06-17 18:21 ` [PATCH v4 1/1] " Kathleen Capella
2022-06-19 12:14 ` Zhang, Qi Z [this message]
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=DM4PR11MB5994B3CAB8353551BA472E6DD7B19@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jingjing.wu@intel.com \
--cc=kathleen.capella@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).