From: Filip Janiszewski <contact@filipjaniszewski.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, users@dpdk.org
Subject: Re: [dpdk-users] Correct setup of sfc
Date: Wed, 13 Jun 2018 21:14:21 +0200 [thread overview]
Message-ID: <d7d4ac5f-802f-667e-9024-656c8cde4f25@filipjaniszewski.com> (raw)
In-Reply-To: <d96fc023-fed4-13d3-1f05-f6ad94fb72d4@solarflare.com>
Hi Andrew,
> PCI devices of Solarflare NIC should be bound to vfio, uio-pci-generic or
> igb_uio (part of DPDK) module. In the case of Solarflare NICs, Linux
> driver is
> not required and not used in DPDK.
>
> So, you should load one of above modules (depending on your server
> IOMMU configuration), push already created interfaces down and rebind
> Solarflare PCI functions to the driver, something like:
>
> modprobe vfio-pci
> ip link set enp101s0f0 down
> ip link set enp101s0f1 down
> dpdk-devbind.py --bind=vfio-pci 0000:65:00.0 0000:65:00.1
>
> The above assumes that dpdk-devbind.py script is in PATH.
> And start DPDK as you do before.
>
For some reason vfio-pci is refusing to bind the device:
.
root usertools : ./dpdk-devbind.py --bind=vfio_pci 0000:65:00.0 0000:65:00.1
Error: bind failed for 0000:65:00.0 - Cannot open
/sys/bus/pci/drivers/vfio_pci/bind
Error: bind failed for 0000:65:00.1 - Cannot open
/sys/bus/pci/drivers/vfio_pci/bind
.
also:
.
root usertools : echo 0000:65:00.0 > /sys/bus/pci/drivers/vfio-pci/bind
bash: echo: write error: No such device
.
In the kernel command line I've included 'iommu=pt intel_iommu=on', but
still not working. Well I guess this is not a DPDK issue anymore.
Thanks!
> Regards,
> Andrew.
--
BR, Filip
+48 666 369 823
next prev parent reply other threads:[~2018-06-13 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 9:46 Filip Janiszewski
2018-06-13 17:46 ` Andrew Rybchenko
2018-06-13 19:14 ` Filip Janiszewski [this message]
2018-06-15 9:44 ` Andrew Rybchenko
2018-06-15 17:02 ` Filip Janiszewski
2018-06-15 17:41 ` Filip Janiszewski
2018-06-15 15:34 ` Rosen, Rami
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=d7d4ac5f-802f-667e-9024-656c8cde4f25@filipjaniszewski.com \
--to=contact@filipjaniszewski.com \
--cc=arybchenko@solarflare.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).