DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Nagaraj Trivedi <nagaraj.trivedi@tcs.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] which driver to bind for the NIC interfacesg
Date: Fri, 29 Jan 2016 10:12:30 -0700	[thread overview]
Message-ID: <20160129171230.GB14384@bricha3-MOBL3> (raw)
In-Reply-To: <OFFB4497F9.8FC608F6-ON65257F45.00457353-65257F45.00464C50@tcs.com>

On Mon, Jan 25, 2016 at 06:17:23PM +0530, Nagaraj Trivedi wrote:
> Hi all, in the Getting Started Guide for Linux, Release 2.2.0 it is 
> mentioned that we need to bind the ports to uio_pci_generic, igb_uio or 
> vfio-pci. 
> 
> I would like to know exactly among uio_pci_generic, igb_uio or vfio-pci to 
> which one I need to bind the port.
> 
> 
This is touched upon in the documentation here:
http://dpdk.org/doc/guides/linux_gsg/build_dpdk.html#loading-modules-to-enable-userspace-io-for-dpdk

The short version is that it depends upon your use-case. In all cases the
igb_uio module should work, but it is an out-of-tree kernel module. Because of
that vfio and uio_pci_generic are better alternatives, but have some restrictions:
* vfio requires an IOMMU be present (though this should change in future kernels)
* uio_pci_generic requires the device have legacy interrupts, so won't work with
  virtual function devices.

If in doubt, and if you don't care about out of tree drivers, just go with
igb_uio to start with.

/Bruce

      reply	other threads:[~2016-01-29 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 12:47 [dpdk-dev] which driver to bind for the NIC interfaces Nagaraj Trivedi
2016-01-29 17:12 ` Bruce Richardson [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=20160129171230.GB14384@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=nagaraj.trivedi@tcs.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).