DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: james_huang黃啟軒 <james_huang@aewin.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: Re: [PATCH] add 23.03 Aewin performance reports
Date: Mon, 26 May 2025 12:02:26 +0200	[thread overview]
Message-ID: <50035813.MN2xkq1pzW@thomas> (raw)
In-Reply-To: <SI2PR04MB4185DCB5FDFFED343C82937F9B65A@SI2PR04MB4185.apcprd04.prod.outlook.com>

OK, thank you for the explanations.

So AEWIN NICs can be used with the DPDK drivers i40e and ice
without any modification?
Don't you have different PCI IDs?


26/05/2025 11:25, james_huang黃啟軒:
> From: Thomas Monjalon <thomas@monjalon.net> 
> 
> > This is a test for a DPDK release which is 2 years old.
> > Why not testing a more recent one?
> 
> => Since the Intel E810 uses DPDK version 23.03, we followed its procedures to validate AEWIN NICs accordingly.

For information, Intel E810 NIC can be use with any DPDK version
since 19.02, including the recent 25.03.

> > 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?
> 
> => Our company's NICs use the Intel® XL710-BM1 and Intel® E810-CAM2 chipsets, so the drivers are based on Intel's. The purpose of uploading to DPDK.org is to increase our company's visibility, allowing our customers to download our performance reports directly from the DPDK website. It also signifies that Intel recognizes the DPDK performance of AEWIN NICs.




  reply	other threads:[~2025-05-26 10:02 UTC|newest]

Thread overview: 6+ 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 [this message]
2025-05-27  1:40       ` james_huang黃啟軒
2025-05-28  1:30         ` james_huang黃啟軒

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=50035813.MN2xkq1pzW@thomas \
    --to=thomas@monjalon.net \
    --cc=james_huang@aewin.com \
    --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).