From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] usertools/dpdk-devbind: add support for PCI wildcards
Date: Tue, 08 Sep 2020 23:44:36 +0200 [thread overview]
Message-ID: <5022801.65yoYiygOP@thomas> (raw)
In-Reply-To: <59412b77-a754-598e-df39-ed444e56fbcb@intel.com>
28/08/2020 17:48, Ferruh Yigit:
> On 8/24/2020 6:04 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>
Applied, thanks
next prev parent reply other threads:[~2020-09-08 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 12:23 [dpdk-dev] [PATCH] usertools/dpdk-devbind: add support for PCI wildcards 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
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 [this message]
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=5022801.65yoYiygOP@thomas \
--to=thomas@monjalon.net \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.