From: james_huang黃啟軒 <james_huang@aewin.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH] add 23.03 Aewin performance reports
Date: Wed, 25 Jun 2025 05:11:43 +0000 [thread overview]
Message-ID: <SEZPR04MB63711849DABEB840FAB2B01C9B7BA@SEZPR04MB6371.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <1866001.yIU609i1g2@thomas>
[-- Attachment #1: Type: text/plain, Size: 2127 bytes --]
Hi Thomas
This is a test for a DPDK release which is 2 years old.
Why not testing a more recent one?
=> We have already conducted testing using the new DPDK 25.03. Please refer to the attached report.
Also, as far as I know, there is no Aewin driver in DPDK, so I'm very surprised.
Are you going to submit some code?
=>
1. The purpose of uploading to DPDK.org is to meet customer expectations, as they want to download AEWIN’s DPDK test reports directly from the official DPDK website. The reason is that customers want to know whether AEWIN’s validated DPDK throughput meets the recognition of DPDK.org.
2. Our network cards are based on the Intel® XL710-BM1 and Intel® E810-CAM2 chipsets, so the drivers are aligned with Intel’s.
3. The main difference is that AEWIN NICs use PCIe Gen4 x8, whereas Intel’s design uses Gen4 x16.
Best Regards
James Huang / SI Engineer
DQA Team
AEWIN Technologies Co., Ltd.
Tel:+886-2-8692-6677 EXT:2011
-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Monday, May 26, 2025 5:07 PM
To: James <csoscar2002@gmail.com>
Cc: web@dpdk.org; james_huang黃啟軒 <james_huang@aewin.com>
Subject: Re: [PATCH] add 23.03 Aewin performance reports
[You don't often get email from thomas@monjalon.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
CAUTION: This email originated from OUTSIDE of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello and welcome,
26/05/2025 10:11, James:
> --- a/content/perf-reports/_index.md
> +++ b/content/perf-reports/_index.md
> @@ -3,6 +3,8 @@ title = "Performance Reports"
> weight = "7"
> +++
>
> ++-[DPDK 23.03 Aewin NIC Performance Report]
> ++
> ++(//fast.dpdk.org/doc/perf/DPDK_23_03_Aewin_NIC_performance_report.pd
> ++f)
This is a test for a DPDK release which is 2 years old.
Why not testing a more recent one?
Also, as far as I know, there is no Aewin driver in DPDK, so I'm very surprised.
Are you going to submit some code?
[-- Attachment #2: AEWIN NICs Performance Report with DPDK 25.03.pdf --]
[-- Type: application/pdf, Size: 799607 bytes --]
next prev parent reply other threads:[~2025-06-29 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 8:11 James
2025-05-26 9:07 ` Thomas Monjalon
2025-05-26 9:25 ` james_huang黃啟軒
2025-05-26 10:02 ` Thomas Monjalon
2025-05-27 1:40 ` james_huang黃啟軒
2025-05-28 1:30 ` james_huang黃啟軒
2025-06-25 5:11 ` james_huang黃啟軒 [this message]
2025-06-25 5:35 ` [PATCH] add 25.03 " james_huang黃啟軒
2025-07-01 11:01 ` [PATCH] add 23.03 " Mcnamara, John
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=SEZPR04MB63711849DABEB840FAB2B01C9B7BA@SEZPR04MB6371.apcprd04.prod.outlook.com \
--to=james_huang@aewin.com \
--cc=thomas@monjalon.net \
--cc=web@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).