From: "Yang, Tao Y" <tao.y.yang@intel.com>
To: Nick Tian <nick.tian@longsailingsemi.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: Isaac Gao <isaac.gao@longsailingsemi.com>,
Jason Liu <jason.liu@longsailingsemi.com>
Subject: RE: 回复：No packet was send out successfully with EB-LINK intel I226
Date: Mon, 22 May 2023 09:34:39 +0000 [thread overview]
Message-ID: <SJ0PR11MB5630F235F8DFC63F6967CD4FDD439@SJ0PR11MB5630.namprd11.prod.outlook.com> (raw)
In-Reply-To: <fab189e5-27af-4159-9144-6fcd5687baa0.nick.tian@longsailingsemi.com>
[-- Attachment #1.1: Type: text/plain, Size: 1854 bytes --]
You can try the uio_pci_generic, don’t use the VFIO-PCI driver.
modprobe uio
modprobe uio_pci_generic
dpdk-devbind.py -b uio_pci_generic xxxx
From: Nick Tian <nick.tian@longsailingsemi.com>
Sent: Monday, May 22, 2023 9:22 AM
To: Nick Tian <nick.tian@longsailingsemi.com>; users@dpdk.org
Cc: Isaac Gao <isaac.gao@longsailingsemi.com>; Jason Liu <jason.liu@longsailingsemi.com>
Subject: 回复：No packet was send out successfully with EB-LINK intel I226
Is there someone know something about this?
-----------------------------------------------------
No packet was sent out successfully with EB-LINK intel I226
------------------原始邮件 ------------------
发件人:Nick Tian <nick.tian@longsailingsemi.com<mailto:nick.tian@longsailingsemi.com>>
发送时间:05/19/23 17:37:34
收件人:users@dpdk.org <users@dpdk.org<mailto:users@dpdk.org>>
抄送:Isaac Gao <isaac.gao@longsailingsemi.com<mailto:isaac.gao@longsailingsemi.com>>, Jason Liu <jason.liu@longsailingsemi.com<mailto:jason.liu@longsailingsemi.com>>
主题:No packet was send out successfully with EB-LINK intel I226
Hi Community:
There is a problem when I use dpdk-testpmd to execute io mode test.
Issue description: No packet was sent out successfully.
testpmd cmdline: dpdk-testpmd -l 1,2,3 -n 4 -- -i
[cid:image001.png@01D98CD3.AAF91920]
test mode setup:"set fwd io" then "start"
[cid:image002.png@01D98CD3.AAF91920]
Statistics: No packet was send out.
[cid:image003.png@01D98CD3.AAF91920]
Environment:
ThinkCentre-E77+ubuntu22.04 64bit@kernel 5.11.0-27-generic + dpdk 22.11.1 + Intel I226 network adapter
Network topology: connect port1 to port2 directly with network cable(No switch was involved).
[cid:image004.png@01D98CD3.AAF91920]
Hugepage:
[cid:image005.png@01D98CD3.AAF91920]
device bind:
[cid:image006.png@01D98CD3.AAF91920]
[-- Attachment #1.2: Type: text/html, Size: 10589 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 45067 bytes --]
[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 53310 bytes --]
[-- Attachment #4: image003.png --]
[-- Type: image/png, Size: 51470 bytes --]
[-- Attachment #5: image004.png --]
[-- Type: image/png, Size: 10582 bytes --]
[-- Attachment #6: image005.png --]
[-- Type: image/png, Size: 21883 bytes --]
[-- Attachment #7: image006.png --]
[-- Type: image/png, Size: 26332 bytes --]
next prev parent reply other threads:[~2023-05-22 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 9:37 No " Nick Tian
2023-05-22 1:21 ` 回复：No " Nick Tian
2023-05-22 9:34 ` Yang, Tao Y [this message]
2023-05-22 10:31 ` 回复：RE: " Nick Tian
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=SJ0PR11MB5630F235F8DFC63F6967CD4FDD439@SJ0PR11MB5630.namprd11.prod.outlook.com \
--to=tao.y.yang@intel.com \
--cc=isaac.gao@longsailingsemi.com \
--cc=jason.liu@longsailingsemi.com \
--cc=nick.tian@longsailingsemi.com \
--cc=users@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).