Virtualization - Dec 2021 - [PATCH v2 00/10] Allow for configuring max number of virtqueue pairs

> From: Jason Wang <jasowang at redhat.com>
> Sent: Tuesday, December 14, 2021 8:47 AM
> 
> A question, consider the parent support both net and block, if user use
> 
> vdpa dev add name vdpa-a mgmtdev auxiliary/mlx5_core.sf.1
> 
> How do we know it's a net or block device? Or do you expect some block
> specific attributes to be added?
User should pass the virtio device id of type net/blk etc when creating the
device.
No such in-kernel driver exists so far, so when it is added netlink interface
should be enhanced to accept the optional device id.

On Tue, Dec 14, 2021 at 12:11 PM Parav Pandit <parav at nvidia.com>
wrote:
>
>
> > From: Jason Wang <jasowang at redhat.com>
> > Sent: Tuesday, December 14, 2021 8:47 AM
> >
> > A question, consider the parent support both net and block, if user
use
> >
> > vdpa dev add name vdpa-a mgmtdev auxiliary/mlx5_core.sf.1
> >
> > How do we know it's a net or block device? Or do you expect some
block
> > specific attributes to be added?
> User should pass the virtio device id of type net/blk etc when creating the
device.
> No such in-kernel driver exists so far, so when it is added netlink
interface should be enhanced to accept the optional device id.
So the plan is to reject the dev adding without specifying the device
type? Looks fine to me.

Thanks