Jason Wang
2020-Jul-16 09:35 UTC
[PATCH vhost next 06/10] vdpa: Add means to communicate vq status on get_vq_state
On 2020/7/16 ??4:21, Eli Cohen wrote:> On Thu, Jul 16, 2020 at 04:11:00PM +0800, Jason Wang wrote: >> On 2020/7/16 ??3:23, Eli Cohen wrote: >>> Currently, get_vq_state() is used only to pass the available index value >>> of a vq. Extend the struct to return status on the VQ to the caller. >>> For now, define VQ_STATE_NOT_READY. In the future it will be extended to >>> include other infomration. >>> >>> Modify current vdpa driver to update this field. >>> >>> Reviewed-by: Parav Pandit<parav at mellanox.com> >>> Signed-off-by: Eli Cohen<eli at mellanox.com> >> What's the difference between this and get_vq_ready()? >> >> Thanks >> > There is no difference. It is just a way to communicate a problem to > with the state of the VQ back to the caller. This is not available now. > I think an asynchronous is preferred but that is not available > currently.I still don't see the reason, maybe you can give me an example? Thanks
Apparently Analagous Threads
- [PATCH vhost next 06/10] vdpa: Add means to communicate vq status on get_vq_state
- [PATCH vhost next 06/10] vdpa: Add means to communicate vq status on get_vq_state
- [PATCH V2 vhost next 06/10] vdpa: Modify get_vq_state() to return error code
- [PATCH V4 linux-next 08/12] vdpa: Modify get_vq_state() to return error code
- [PATCH v2 1/2] vdpa/mlx5: Extend driver support for new features