DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc/devbind: remove references to igb_uio
Date: Wed, 14 Oct 2020 17:43:29 +0100	[thread overview]
Message-ID: <bbf44a3e-34e1-f70e-951b-8ac8a123517b@intel.com> (raw)
In-Reply-To: <20200924175347.13619-1-stephen@networkplumber.org>

On 9/24/2020 6:53 PM, Stephen Hemminger wrote:
> We should be encouraging the use of vfio_pci for developers, not telling
> them to use igb_uio.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> v2 -- drop change about filename
> 
>   doc/guides/tools/devbind.rst | 18 +++++++++---------
>   1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/doc/guides/tools/devbind.rst b/doc/guides/tools/devbind.rst
> index a2910e103aab..5dcaf8c207dd 100644
> --- a/doc/guides/tools/devbind.rst
> +++ b/doc/guides/tools/devbind.rst
> @@ -30,11 +30,11 @@ OPTIONS
>           Print the current status of all known network interfaces.
>           For each device, it displays the PCI domain, bus, slot and function,
>           along with a text description of the device. Depending upon whether the
> -        device is being used by a kernel driver, the ``igb_uio`` driver, or no
> +        device is being used by a kernel driver, the ``vfio_pci`` driver, or no
>           driver, other relevant information will be displayed:
>           - the Linux interface name e.g. ``if=eth0``
> -        - the driver being used e.g. ``drv=igb_uio``
> -        - any suitable drivers not currently using that device e.g. ``unused=igb_uio``
> +        - the driver being used e.g. ``drv=vfio_pci``
> +        - any suitable drivers not currently using that device e.g. ``unused=vfio_pci``
>           NOTE: if this flag is passed along with a bind/unbind option, the
>           status display will always occur after the other operations have taken
>           place.
> @@ -80,9 +80,9 @@ To display current device status::
>   
>      dpdk-devbind --status
>   
> -To bind eth1 from the current driver and move to use igb_uio::
> +To bind eth1 from the current driver and move to use vfio_pci::
>   
> -   dpdk-devbind --bind=igb_uio eth1
> +   dpdk-devbind --bind=vfio_pci eth1

Module name is 'vfio_pci' but driver name is 'vfio-pci', for this document I 
guess all instances should be 'vfio-pci'.

>   
>   To unbind 0000:01:00.0 from using any driver::
>   
> @@ -92,7 +92,7 @@ To bind 0000:02:00.0 and 0000:02:00.1 to the ixgbe kernel driver::
>   
>      dpdk-devbind -b ixgbe 02:00.0 02:00.1
>   
> -To check status of all network ports, assign one to the igb_uio driver and check status again::
> +To check status of all network ports, assign one to the vfio_pci driver and check status again::
>   
>      # Check the status of the available devices.
>      dpdk-devbind --status
> @@ -105,12 +105,12 @@ To check status of all network ports, assign one to the igb_uio driver and check
>      0000:0a:00.0 '82599ES 10-Gigabit' if=eth2 drv=ixgbe unused=
>   
>   
> -   # Bind the device to igb_uio.
> -   sudo dpdk-devbind -b igb_uio 0000:0a:00.0
> +   # Bind the device to vfio_pci.
> +   sudo dpdk-devbind -b vfio_pci 0000:0a:00.0
>   
>   
>      # Recheck the status of the devices.
>      dpdk-devbind --status
>      Network devices using DPDK-compatible driver
>      ============================================
> -   0000:0a:00.0 '82599ES 10-Gigabit' drv=igb_uio unused=
> +   0000:0a:00.0 '82599ES 10-Gigabit' drv=vfio_pci unused=
> 


  reply	other threads:[~2020-10-14 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06  3:38 [dpdk-dev] [PATCH] " Stephen Hemminger
2020-09-07  9:08 ` Bruce Richardson
2020-09-07 17:22   ` Stephen Hemminger
2020-09-24 17:53 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2020-10-14 16:43   ` Ferruh Yigit [this message]
2020-11-26 11:48     ` Bruce Richardson
2020-11-26 16:00       ` David Marchand

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=bbf44a3e-34e1-f70e-951b-8ac8a123517b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).