DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] usertools/dpdk-devbind: add support for PCI wildcards
Date: Fri, 21 Aug 2020 10:17:14 +0100	[thread overview]
Message-ID: <b1d7b919-b520-a618-6954-c0b331cf899e@intel.com> (raw)
In-Reply-To: <20200820154308.3212-1-bruce.richardson@intel.com>

On 20-Aug-20 4:43 PM, Bruce Richardson wrote:
> When binding or unbinding a range of devices, it can be useful to use
> wildcards to specify the devices rather than repeating the same prefix
> multiple times. We can use the python "glob" module to give us this
> functionality - at least for PCI devices - by checking /sys for matching
> files.
> 
> Examples of use from my system:
> 
>      ./dpdk-devbind.py -b vfio-pci 80:04.*
>      ./dpdk-devbind.py -u 80:04.[2-7]
> 
> The first example binds eight devices, 80:04.0..80:04.7, to vfio-pci. The
> second then unbinds six of those devices, 80:04.2..80:04.7, from any
> driver.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> V2: added help text additions
> ---
>   usertools/dpdk-devbind.py | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
> 
> diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
> index 86b6b53c40..d13defbe1a 100755
> --- a/usertools/dpdk-devbind.py
> +++ b/usertools/dpdk-devbind.py
> @@ -8,6 +8,7 @@
>   import os
>   import getopt
>   import subprocess
> +from glob import glob
>   from os.path import exists, abspath, dirname, basename
>   
>   if sys.version_info.major < 3:
> @@ -89,6 +90,8 @@ def usage():
>   where DEVICE1, DEVICE2 etc, are specified via PCI "domain:bus:slot.func" syntax
>   or "bus:slot.func" syntax. For devices bound to Linux kernel drivers, they may
>   also be referred to by Linux interface name e.g. eth0, eth1, em0, em1, etc.
> +If devices are specified using PCI <domain:>bus:device:func format, then
> +shell wildcards and ranges may be used, e.g. 80:04.*, 80:04.[0-3]
>   
>   Options:
>       --help, --usage:
> @@ -145,6 +148,9 @@ def usage():
>   To bind 0000:02:00.0 and 0000:02:00.1 to the ixgbe kernel driver
>           %(argv0)s -b ixgbe 02:00.0 02:00.1
>   
> +To bind all funcions on device 0000:02:00 to ixgbe kernel driver
> +        %(argv0)s -b ixgbe 02:00.*
> +
>       """ % locals())  # replace items from local variables
>   
>   
> @@ -689,6 +695,16 @@ def parse_args():
>               else:
>                   b_flag = arg
>   
> +    # resolve any PCI globs in the args
> +    new_args = []
> +    sysfs_path = "/sys/bus/pci/devices/"
> +    for arg in args:
> +        globbed_arg = glob(sysfs_path + arg) + glob(sysfs_path + "0000:" + arg)

Also, could be

glob_path = arg if arg.startswith("0000:") else "0000:" + arg
globbed_arg = glob(os.path.join(sysfs_path, glob_path))

No need to glob twice :)

> +        if globbed_arg:
> +            new_args.extend([a[len(sysfs_path):] for a in globbed_arg])
> +        else:
> +            new_args.append(arg)
> +    args = new_args
>   
>   def do_arg_actions():
>       '''do the actual action requested by the user'''
> 


-- 
Thanks,
Anatoly

  parent reply	other threads:[~2020-08-21  9:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 12:23 [dpdk-dev] [PATCH] " Bruce Richardson
2020-08-20 14:44 ` Ferruh Yigit
2020-08-20 15:43   ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2020-08-21  9:14     ` Burakov, Anatoly
2020-08-24 17:05       ` Bruce Richardson
2020-08-21  9:17     ` Burakov, Anatoly [this message]
2020-08-24 16:19       ` Bruce Richardson
2020-08-20 15:43   ` [dpdk-dev] [PATCH] " Bruce Richardson
2020-08-20 15:52   ` [dpdk-dev] [PATCH v3] " Bruce Richardson
2020-08-24 17:04 ` [dpdk-dev] [PATCH v4] " Bruce Richardson
2020-08-28 15:48   ` Ferruh Yigit
2020-09-08 21:44     ` Thomas Monjalon
2020-08-28 16:02   ` Burakov, Anatoly

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=b1d7b919-b520-a618-6954-c0b331cf899e@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).