[dpdk-dev] [PATCH] doc: document the new devargs syntax

Thomas Monjalon thomas at monjalon.net
Wed Jan 17 00:22:43 CET 2018


17/01/2018 00:19, Gaëtan Rivet:
> Hi Yuanhan,
> 
> On Tue, Jan 16, 2018 at 10:50:18PM +0800, Yuanhan Liu wrote:
> > +The ``devargs`` can be used for whitelisting/blacklisting devices, identifying
> > +DPDK ports and attaching/deatching devices. They all share the same syntax.
> > +
> > +It is split in 3 categories, where almost everything is optional key/value pairs:
> > +
> > +* bus (pci, vdev, vmbus, fslmc, etc)
> > +* class (eth, crypto, etc)
> > +* driver (i40e, mlx5, virtio, etc)
> > +
> > +The key/value pair describing the category scope is mandatory and must be the
> > +first pair in the category properties. Example: bus=pci, must be placed before
> > +id=0000:01:00.0.
> > +
> > +The syntax has below rules:
> > +
> > +* Between categories, the separator is a slash.
> > +* Inside a category, the separator is a comma.
> > +* Inside a key/value pair, the separator is an equal sign.
> > +* Each category can be used alone.
> > +
> > +Here is an example with all categories::
> > +
> > +    bus=pci,id=0000:01:00.0/class=eth,mac=00:11:22:33:44:55/driver=PMD_NAME,driverspecificproperty=VALUE
> > +
> 
> It might be a nitpick, but the driver specific properties might not
> follow the key/value pair syntax. At least for the fail-safe, a custom
> parsing needs to happen. I think vdev in general will need flexibility.

What is more flexible than key/value?

> There could be a note that after the comma past the eventual
> "driver=xxxx" pair, the syntax is driver-specific and might not follow
> the equal-separated key/value pair syntax.

Please give an example.


More information about the dev mailing list