search for: virito_mdev_device_ops

...irtio-mdev transport to userspace. > > Currently, virtio-mdev transport is a set of function callbacks > > defined in kernel. How to simply expose virtio-mdev transport to > > userspace? > > > The most straightforward way is to have an 1:1 mapping between ioctl and > virito_mdev_device_ops. Seems we are already trying to do 1:1 mapping between ioctl and virtio_mdev_device_ops in vhost-mdev now (the major piece missing is get_device_id/get_config/set_config). > > Thanks > > > > > > > > > A generic module > > > without any type specific...

...irtio-mdev transport to userspace. > > Currently, virtio-mdev transport is a set of function callbacks > > defined in kernel. How to simply expose virtio-mdev transport to > > userspace? > > > The most straightforward way is to have an 1:1 mapping between ioctl and > virito_mdev_device_ops. Seems we are already trying to do 1:1 mapping between ioctl and virtio_mdev_device_ops in vhost-mdev now (the major piece missing is get_device_id/get_config/set_config). > > Thanks > > > > > > > > > A generic module > > > without any type specific...

...t; >> 3) Simply expose all virtio-mdev transport to userspace. > Currently, virtio-mdev transport is a set of function callbacks > defined in kernel. How to simply expose virtio-mdev transport to > userspace? The most straightforward way is to have an 1:1 mapping between ioctl and virito_mdev_device_ops. Thanks > > >> A generic module >> without any type specific code (like virtio-mdev). No need dedicated API for >> e.g MQ. But then the API will look much different than current vhost did. >> >> Consider the limitation of 1) I tend to choose 2 or 3. What's...

On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote: > On 2019/10/23 ??11:02, Tiwei Bie wrote: > > On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > > > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > > > This patch introduces a mdev based hardware vhost backend. > > > > This backend is built on top of the same abstraction used > > >

On Wed, Oct 23, 2019 at 01:46:23PM +0800, Jason Wang wrote: > On 2019/10/23 ??11:02, Tiwei Bie wrote: > > On Tue, Oct 22, 2019 at 09:30:16PM +0800, Jason Wang wrote: > > > On 2019/10/22 ??5:52, Tiwei Bie wrote: > > > > This patch introduces a mdev based hardware vhost backend. > > > > This backend is built on top of the same abstraction used > > >

...Currently, virtio-mdev transport is a set of function callbacks > > > > defined in kernel. How to simply expose virtio-mdev transport to > > > > userspace? > > > > > > The most straightforward way is to have an 1:1 mapping between ioctl and > > > virito_mdev_device_ops. > > Seems we are already trying to do 1:1 mapping between ioctl > > and virtio_mdev_device_ops in vhost-mdev now (the major piece > > missing is get_device_id/get_config/set_config). > > > Yes, with this we can have a device independent API. Do you think this is > b...

...Currently, virtio-mdev transport is a set of function callbacks > > > > defined in kernel. How to simply expose virtio-mdev transport to > > > > userspace? > > > > > > The most straightforward way is to have an 1:1 mapping between ioctl and > > > virito_mdev_device_ops. > > Seems we are already trying to do 1:1 mapping between ioctl > > and virtio_mdev_device_ops in vhost-mdev now (the major piece > > missing is get_device_id/get_config/set_config). > > > Yes, with this we can have a device independent API. Do you think this is > b...

...nsport to userspace. >>> Currently, virtio-mdev transport is a set of function callbacks >>> defined in kernel. How to simply expose virtio-mdev transport to >>> userspace? >> >> The most straightforward way is to have an 1:1 mapping between ioctl and >> virito_mdev_device_ops. > Seems we are already trying to do 1:1 mapping between ioctl > and virtio_mdev_device_ops in vhost-mdev now (the major piece > missing is get_device_id/get_config/set_config). Yes, with this we can have a device independent API. Do you think this is better? Thanks > > >&gt...

...t;>> Currently, virtio-mdev transport is a set of function callbacks >>>>> defined in kernel. How to simply expose virtio-mdev transport to >>>>> userspace? >>>> The most straightforward way is to have an 1:1 mapping between ioctl and >>>> virito_mdev_device_ops. >>> Seems we are already trying to do 1:1 mapping between ioctl >>> and virtio_mdev_device_ops in vhost-mdev now (the major piece >>> missing is get_device_id/get_config/set_config). >> >> Yes, with this we can have a device independent API. Do you think this...