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 v2 1/1] net/iavf: add vector PMD for Arm for basic Rx path
Date: Sun, 29 May 2022 22:56:38 +0000 [thread overview]
Message-ID: <DM4PR11MB59940E5BC561FE5CDE859BB6D7DA9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220525190954.30435-2-kathleen.capella@arm.com>
> -----Original Message-----
> From: Kathleen Capella <kathleen.capella@arm.com>
> Sent: Thursday, May 26, 2022 3:10 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 v2 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 testpmd mac forwarding and saw Rx-pps =
> 20M.
Could you share which NIC / Bandwidth is used in N1SDP platform ?
Is 20M is from a single core testing? how much performance improvement compare to scalar path?
next prev parent reply other threads:[~2022-05-29 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 19:09 [PATCH v2 0/1] " Kathleen Capella
2022-05-25 19:09 ` [PATCH v2 1/1] " Kathleen Capella
2022-05-29 22:56 ` Zhang, Qi Z [this message]
2022-06-07 8:55 ` Zhang, Qi Z
2022-06-16 19:34 ` Kathleen Capella
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=DM4PR11MB59940E5BC561FE5CDE859BB6D7DA9@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).