DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] A Question about the necessity of DPDK VF for Ethernet PMDs
Date: Mon, 4 Feb 2019 10:22:30 +0000	[thread overview]
Message-ID: <CAD+H992VV2hmkhi1D250+ucN2O4ZY6G5-phKuNMmSG1qekzuBw@mail.gmail.com> (raw)
In-Reply-To: <CAHLOa7SnR+4hDzVPuEnTXPxCxurbqXGinP9jCk8XzjEWkiSEYw@mail.gmail.com>

Hi Rami,

Your concern is related to this thread:

http://mails.dpdk.org/archives/dev/2019-January/123466.html

I'm working on solving the problem when PF needs to be bound to VFIO. My
proposal is to use mediated devices.
Although it is not strictly necessary to rely on current kernel WiP about
VFIO med-devices IOMMU aware

https://lwn.net/Articles/763793/

using that patch makes the implementation easier. Indeed, this solution
implies changes to current kernel netdev drivers, and the previous
commented kernel patch will likely be accepted upstream before our push.

DPDK changes for supporting mdev bus will happen soon (I hope). Intel guys
are working on this for the I/O scale case Intel is interested in, with
Netronome's case, and the one you point out, being a specific case which
can be implemented with those DPDK and kernel changes.


On Mon, Feb 4, 2019 at 7:43 AM Rami Rosen <ramirose@gmail.com> wrote:

>  Hello all,
>
>
>
> Now that DPDK 19.02 was released three days ago (on time!!), hopefully
> there will be time
>
> for people to answer the following question:
>
>
>
> According to the "DPDK Getting Started Guide",
>
>
>
> "If UEFI secure boot is enabled, the Linux kernel may disallow the use of
> UIO on the system.
>
> Therefore, devices for use by DPDK should be bound to the vfio-pci kernel
> module
>
> rather than igb_uio or uio_pci_generic. For more details see Binding and
>
> Unbinding Network Ports to/from the Kernel Modules."
>
> See:
>
>
> http://doc.dpdk.org/guides/linux_gsg/sys_reqs.html#bios-setting-prerequisite-on-x86
>
>
>
> Now, when you bind a PCI device with vfio-pci, then the "max_vfs" entry is
> *not* created under
>
> /sys/bus/pci/devices/<BDF>/ (as opposed to the case when you bind with
> igb_uio).
>
> This means that you cannot create DPDK VFS in this case (as you cannot
> write num_vfs to the
>
> non existing max_vfs entry). You can however create Kernel VFs (by echoing
> into the sriov_num_vfs
>
> sysfs entry).
>
>
>
> So I assume there are deployments of DPDK (with secure boot) when the PMDs
> are being binded not by
>
> igb_uio but by vfio_pci.
>
>
>
> So the question is:
>
> As explained above, t probably there are setups when you cannot generated
> PMD VFs.
>
> Most PMD Ethernet Vendors *do* provide VF PMDs in the DPDK official repo;
>
> but what are the benefits of providing DPDK VFs PMD? is it mandatory in
> some use cases ?
>
> Is there any advantage for using a DPDK PF/DPDK VF
>
> combination over using Kernel VF?
>
>
>
> Regards,
>
> Rami Rosen
>

  reply	other threads:[~2019-02-04 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  7:43 Rami Rosen
2019-02-04 10:22 ` Alejandro Lucero [this message]
2019-02-04 10:44   ` Rami Rosen
2019-02-04 11:30     ` Alejandro Lucero
2019-02-04 12:19       ` Rami Rosen
2019-02-04 12:53         ` Alejandro Lucero

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=CAD+H992VV2hmkhi1D250+ucN2O4ZY6G5-phKuNMmSG1qekzuBw@mail.gmail.com \
    --to=alejandro.lucero@netronome.com \
    --cc=dev@dpdk.org \
    --cc=ramirose@gmail.com \
    /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).