From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 09/11] device-args: replace use-device eal option by pci-whitelist and vdev
Date: Mon, 3 Mar 2014 17:14:44 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01A9A16C7@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1393608350-4431-10-git-send-email-olivier.matz@6wind.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz
> Sent: Friday, February 28, 2014 5:26 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 09/11] device-args: replace use-device eal
> option by pci-whitelist and vdev
>
> This commit splits the "--use-device" option in two new options:
>
> - "--pci-whitelist or -w": add a PCI device in the white list
> - "--vdev": instanciate a new virtual device
>
> Before the patch, the same option "--use-device" was used for these 2 use-
> cases.
[BR] Reviewing the patch set, most of the changes make sense to me. This one I've a few comments on.
Is it really necessary and beneficial to split the --use-device option into two, and have two different ways for specifying the devices to use, based on whether they are pci or virtual devices? An alternative suggestion/idea: keep a common flag (be it --use-device, or something else) to specify a device to use and that device's parameters, for all device types, pretty much as now. Then, to solve the issue of not being able to use blacklisting plus virtual devices, that could be solved by adding the --pci-whitelist like you suggest, except instead of specifying the devices there, it simply means that only the pci devices passed to use-device get used. Without --pci-whitelist, all pci devices get used, whether or not they are explicitly called out with --use-device?
In this case, the "-b" flag could also be aliased by an "--ignore-device" (or similar) flag.
Any other thoughts or suggestions?
next prev parent reply other threads:[~2014-03-03 17:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 17:25 [dpdk-dev] [PATCH 00/11] eal: allow virtual pmd drivers as shared lib Olivier Matz
2014-02-28 17:25 ` [dpdk-dev] [PATCH 01/11] mk: use whole-archive option when creating dpdk binaries Olivier Matz
2014-04-10 13:58 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 02/11] devices-args: introduce rte_devargs in eal Olivier Matz
2014-02-28 21:39 ` Stephen Hemminger
2014-03-01 12:02 ` Olivier MATZ
2014-03-01 12:14 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2014-04-10 13:59 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 03/11] devices-args: use rte_devargs and remove old whitelist code Olivier Matz
2014-03-01 12:14 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2014-04-10 14:01 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 04/11] devices-args: add a dump_devargs command in basic test application Olivier Matz
2014-04-10 14:02 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 05/11] pci: rename device_list as pci_device_list Olivier Matz
2014-04-10 14:03 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 06/11] vdev: rename eal_common_nonpci_devs.c as eal_common_vdev.c Olivier Matz
2014-04-10 14:39 ` Thomas Monjalon
2014-04-11 7:36 ` [dpdk-dev] [PATCH v2 06/11] vdev: rename nonpci_devs as vdev Olivier Matz
2014-04-11 11:25 ` Thomas Monjalon
2014-04-11 11:45 ` [dpdk-dev] [PATCH v3 " Olivier Matz
2014-04-11 12:37 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 07/11] vdev: allow external registration of virtual device drivers Olivier Matz
2014-04-10 14:55 ` Thomas Monjalon
2014-04-11 7:36 ` [dpdk-dev] [PATCH v2 07/11 1/2] vdev: new registration API Olivier Matz
2014-04-11 7:36 ` [dpdk-dev] [PATCH v2 07/11 2/2] vdev: allow external registration of virtual device drivers Olivier Matz
2014-04-11 14:31 ` Thomas Monjalon
2014-04-11 10:49 ` [dpdk-dev] [PATCH v2 07/11 1/2] vdev: new registration API Neil Horman
2014-04-11 13:11 ` Thomas Monjalon
2014-04-11 15:50 ` Neil Horman
2014-04-11 16:18 ` Thomas Monjalon
2014-04-11 17:44 ` Neil Horman
2014-04-11 20:08 ` Richardson, Bruce
2014-04-12 6:05 ` Thomas Monjalon
2014-04-12 11:03 ` Neil Horman
2014-04-12 11:23 ` Richardson, Bruce
2014-04-12 14:06 ` Neil Horman
2014-04-14 13:20 ` John W. Linville
2014-04-14 13:45 ` Thomas Monjalon
2014-04-14 13:54 ` Neil Horman
2014-04-14 14:10 ` John W. Linville
2014-04-14 14:39 ` Thomas Monjalon
2014-04-11 14:31 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 08/11] device-args: use a comma instead of semicolon to separate key/values Olivier Matz
2014-04-10 14:05 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 09/11] device-args: replace use-device eal option by pci-whitelist and vdev Olivier Matz
2014-03-01 12:14 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2014-04-10 14:06 ` Thomas Monjalon
2014-03-03 17:14 ` Richardson, Bruce [this message]
2014-03-04 13:09 ` [dpdk-dev] [PATCH " Olivier MATZ
2014-03-04 13:14 ` Richardson, Bruce
2014-03-24 22:39 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 10/11] device-args: allow to provide per pci device command line arguments Olivier Matz
2014-03-01 12:14 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2014-04-10 14:06 ` Thomas Monjalon
2014-02-28 17:25 ` [dpdk-dev] [PATCH 11/11] testpmd: add several dump commands, useful for debug Olivier Matz
2014-03-01 12:15 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2014-04-10 14:08 ` Thomas Monjalon
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=59AF69C657FD0841A61C55336867B5B01A9A16C7@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).