DPDK patches and discussions
 help / color / mirror / Atom feed
From: "SamChen 陳嘉良" <SamChen@aaeon.com.tw>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: DPDK with i225/226 on elkhartlake
Date: Thu, 22 Sep 2022 02:56:56 +0000	[thread overview]
Message-ID: <SI2PR02MB582674ACA9D4EC406736C61F834E9@SI2PR02MB5826.apcprd02.prod.outlook.com> (raw)
In-Reply-To: <YyrR2eZ7pz1qSGZ9@bricha3-MOBL.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Hi all,
I have switched to using vfio-pci, but still can't use DPDK. Attached are the logs I can't use in I225-IT and I226V for your reference.
If I have obtained other platforms with intel 225/226 systems, I will check again, thanks!

Sam Chen

-----Original Message-----
From: Bruce Richardson <bruce.richardson@intel.com> 
Sent: Wednesday, September 21, 2022 4:57 PM
To: SamChen 陳嘉良 <SamChen@aaeon.com.tw>
Cc: dev@dpdk.org
Subject: Re: DPDK with i225/226 on elkhartlake

On Wed, Sep 21, 2022 at 03:23:09AM +0000, SamChen 陳嘉良 wrote:
>    Hi,
>    We bind the uio_pci_generic driver and use the command of the attached
>    image to execute DPDK. However, we encountered the problem of device
>    cannot be used on i225V/i226V in elkhartlake platform. Currently, the
>    same method works fine for i211 and intel® Killer™ Ethernet E3100 2.5
>    Gbps. Do you have any suggestions? Thanks!
> 
Hi,

while I can't comment on the NIC-specific issues, I would just comment that it's really not recommended to use uio_pci_generic - or any other uio driver - for DPDK any more. You should consider switching to using vfio-pci. Even if there is no iommu enabled, vfio-pci still tends to give a better user experience. If iommu is enabled, you also get a lot more security from the memory protection it provides.

Regards,
/Bruce

[-- Attachment #2: i225-IT_log --]
[-- Type: application/octet-stream, Size: 1005 bytes --]

[nsd@localhost ~]$ sudo su
[sudo] password for nsd: 
[root@localhost nsd]# modprobe vfio-pci
[root@localhost nsd]# cd dpdk-22.07/usertools/
[root@localhost usertools]# ./dpdk-devbind.py -b vfio-pci 01:00.0 02:00.0
[root@localhost usertools]# cd ../build/app/
[root@localhost app]# ./dpdk-testpmd -l 0-1 -n 1
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
No commandline core given, start packet forwarding
io packet forwarding - ports=0 - cores=0 - streams=0 - NUMA support enabled, MP allocation mode: native

  io packet forwarding packets/burst=32
  nb forwarding cores=1 - nb forwarding ports=0
Press enter to exit


[-- Attachment #3: i226V_log --]
[-- Type: application/octet-stream, Size: 963 bytes --]

[nsd@localhost ~]$ sudo su
[sudo] password for nsd: 
[root@localhost nsd]# modprobe vfio-pci
[root@localhost nsd]# cd dpdk-22.07/usertools/
[root@localhost usertools]# ./dpdk-devbind.py -b vfio-pci 03:00.0 06:00.0
[root@localhost usertools]# cd ../build/app/
[root@localhost app]# ./dpdk-testpmd -l 0-1 -n 1
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_igc (8086:125c) device: 0000:03:00.0 (socket 0)
EAL: Releasing PCI mapped resource for 0000:03:00.0
EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x1100800000
EAL: Calling pci_unmap_resource for 0000:03:00.0 at 0x1100900000
EAL: Requested device 0000:03:00.0 cannot be used
EAL: Using IOMMU type 1 (Type 1)
EAL: Probe PCI driver: net_igc (8086:125c) device: 0000:06:00.0 (socket 0)


  reply	other threads:[~2022-09-22  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  3:23 SamChen 陳嘉良
2022-09-21  8:56 ` Bruce Richardson
2022-09-22  2:56   ` SamChen 陳嘉良 [this message]
2022-09-23  7:50     ` Yang, Qiming
2022-09-23  8:28       ` SamChen 陳嘉良

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=SI2PR02MB582674ACA9D4EC406736C61F834E9@SI2PR02MB5826.apcprd02.prod.outlook.com \
    --to=samchen@aaeon.com.tw \
    --cc=bruce.richardson@intel.com \
    --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).