[dpdk-dev] [PATCH 2/4] bus/vdev: bus scan by multi-process channel
Burakov, Anatoly
anatoly.burakov at intel.com
Mon Mar 5 10:36:37 CET 2018
On 04-Mar-18 3:30 PM, Jianfeng Tan wrote:
> To scan the vdevs in primary, we send request to primary process
> to obtain the names for vdevs.
>
> Only the name is shared from the primary. In probe(), the device
> driver is supposed to locate (or request more) the detail
> information from the primary.
>
> Signed-off-by: Jianfeng Tan <jianfeng.tan at intel.com>
> ---
Is there much point in having private vdevs? Granted, i'm not exactly a
heavy user of vdev's, but to me this would seem like a way to introduce
more confusion. How do i tell which devices are shared between
processes, and which are private to one process? Can i control which one
do i get? To me it would seem like it would be better to just switch all
vdevs to being shared.
--
Thanks,
Anatoly
More information about the dev
mailing list