DPDK usage discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: "Wu, Xiaoban" <Xiaoban_Wu@student.uml.edu>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Mellanox 100G NIC, VF SR-IOV, docker container, EAL could not detect the device
Date: Wed, 24 May 2017 09:51:22 +0200	[thread overview]
Message-ID: <20170524075122.GF1758@6wind.com> (raw)
In-Reply-To: <BN6PR02MB2706D73793AA2FD224F5FE64BCFE0@BN6PR02MB2706.namprd02.prod.outlook.com>

On Wed, May 24, 2017 at 01:01:58AM +0000, Wu, Xiaoban wrote:
> Hi Adrien,
> 
> 
> Thanks very much for your reply.
> 
> 
> However, after the -w option is used, the EAL still could not find the VF devices.
> 
> $dpdk-app -c 0x01 --socket-mem=128,128 --file-prefix="docker1" -w 0000:83:00.1
> 
> 
> EAL: Detected 12 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> PMD: bnxt_rte_pmd_init() called for (null)
> Error, rte_eth_dev_configure() returns negative!

I didn't take Docker into account. Since there is no VM involved, you must
*not* bind the devices to vfio-pci (do not run dpdk-devbind.py, no need to
even modprobe vfio-pci).

With mlx4/mlx5, doing so is only necessary when you intent to assign devices
to a VM, otherwise the spawned VFs must remain managed by their original
kernel drivers. You likely need to transfer the associated netdevices to
your Docker instance for this to work though. You'll likely need to somehow
transfer the related IB instances as well.

At least that's the theory, I've never personally tried to use Docker with
mlx4/mlx5 VFs.

-- 
Adrien Mazarguil
6WIND

      reply	other threads:[~2017-05-24  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  5:39 Wu, Xiaoban
2017-05-23  8:12 ` Adrien Mazarguil
2017-05-24  1:01   ` Wu, Xiaoban
2017-05-24  7:51     ` Adrien Mazarguil [this message]

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=20170524075122.GF1758@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=Xiaoban_Wu@student.uml.edu \
    --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).