Burakov, Anatoly, Aug 20, 2024 at 11:56:
Actually, I should correct myself (and yourself) somewhat.
This is not obvious from help message (I found it through reading the
REAME) but driverctl *does* allow listing PCI devices by type, but only
one type (e.g. list all network devices), but not multiple (e.g. list
network and mempool devices), and as far as I can tell it does not
support some of the device classes that we're interested in, so we will
have to use the entire PCI device list and then filter it.
It does also print out device names (adding "verbose" option does it).
And it also *does* allow to bind/unbind drivers without persistence -
--nosave option does that.
Hehe, I had glanced over this option on the man page but didn't pay
attention. Thanks!
Still, all of the other points apply: devbind is much more useful for
DPDK developers as it provides information relevant to us right out of
the box.
Let's keep it as it is then. No need to impose another dependency. The
driver override code isn't that complicated.
