dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Ifen.Chiang <Ifen.Chiang@advantech.com.tw>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: do you have Intel i226LM 2.5G DPDK RFC-2544 result for us reference?
Date: Thu, 15 Dec 2022 07:30:27 +0000	[thread overview]
Message-ID: <5e046aea20914317b03591ff6d0b4f3f@advantech.com.tw> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3009 bytes --]

Hi dpdk dev team,
This is ifen from Advantech.

We have a question about i226 dpdk test result and want to know the i226LM 2.5G dpdk test result.
Intel suggest us to check dpdk.org directly.

But we don’t know who is the right contact window for us asking.. will you please help forward my mail to the right contact windows?

Our result and test config is in following.
we didn’t get our expectation result. [we expected 2.5G x 2 port testing, frameloss shall be 0 at 256B 100% to 1518B 100%]
Do you have your official i226 dpdk test result for us reference? Or maybe you can give us some suggestion about our test config or environment.

Thanks a lot..

b/r,
ifen


Ø   testpmd  2.5G Frameloss/Throughput Result:
Frame
Size

Frameloss

Throughput

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

64byte

0

0

0

0

0

0

12.772

23.676

32.157

38.942

61.035%

128byte

0

0

0

0

0

0

0

0

8.847

17.96

82.031%

256byte

0

0

0

0

0

0

0

0

0

1.067

98.926%

512byte

0

0

0

0

0

0

0

0

0

0.544

99.414%

1024byte

0

0

0

0

0

0

0

0

0

0.253

99.707%

1280byte

0

0

0

0

0

0

0

0

0

0.188

99.805%

1518byte

0

0

0

0

0

0

0

0

0

0.145

99.805%



Ø   testpmd LAN port speed 1G with our IXIA 1G module
Frame
Size

Frameloss

Throughput

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

64byte

0

0

0

0

0

0

0

0

0

0

100%

128byte

0

0

0

0

0

0

0

0

0

0

100%

256byte

0

0

0

0

0

0

0

0

0

0

100%

512byte

0

0

0

0

0

0

0

0

0

0

100%

1024byte

0

0

0

0

0

0

0

0

0

0

100%

1280byte

0

0

0

0

0

0

0

0

0

0

100%

1518byte

0

0

0

0

0

0

0

0

0

0

100%


Our Detail config/environment:

1.          CPU Name,
=> model name : Intel Atom(R) P5322 processor

cpu MHz: 2200.000

Core Enabled: 8

1.          Memory size, num:
=> Micron 1Rx4 PC4-2933, 16G*2

2.          Huge page size:
=> default_hugepagesz=1G hugepagesz=1G hugepages=16

3.          DPDK version:
=> 22.07

4.          NIC FW:
=> 2014:8877

5.           [LAN controller firmware](e.g., FXVL_125B_LM_2MB_2.17.bin):

=> LAN FW version: 2014:8877 [FXVL_125B_LM_2MB_2.14]

6.       9. [LAN driver version]:

=> igc 5.15.0-40-generic

7.           [OS/Kernel] (e.g., Yocto/Ubuntu 20.04, Linux Kernel version 5.16.18):
=> Ubuntu22.04, 5.15.0-40-generic

8.          Data flow:
IXIA port_1 <------copper cable---> DUT’s i226 Port_1 < ----dpdk-testpmd fwd  ------> DUT’s i226 Port_2 <------copper cable---> IXIA port_2

9.          NIC diagram:
=>
[cid:image010.png@01D90EFB.BBC72130]

b/r,
Ifen


[-- Attachment #1.2: Type: text/html, Size: 101620 bytes --]

[-- Attachment #2: image010.png --]
[-- Type: image/png, Size: 12992 bytes --]

                 reply	other threads:[~2022-12-18 10:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5e046aea20914317b03591ff6d0b4f3f@advantech.com.tw \
    --to=ifen.chiang@advantech.com.tw \
    --cc=dev@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).