Displaying 5 results from an estimated 5 matches for "virtio_user_ethdev".
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
On 2019/10/24 ??4:03, Jason Wang wrote:
>
> On 2019/10/24 ??12:21, Tiwei Bie wrote:
>> On Wed, Oct 23, 2019 at 06:29:21PM +0800, Jason Wang wrote:
>>> On 2019/10/23 ??6:11, Tiwei Bie wrote:
>>>> On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote:
>>>>> On 2019/10/23 ??3:07, Tiwei Bie wrote:
>>>>>> On Wed, Oct 23, 2019 at
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
On 2019/10/24 ??4:03, Jason Wang wrote:
>
> On 2019/10/24 ??12:21, Tiwei Bie wrote:
>> On Wed, Oct 23, 2019 at 06:29:21PM +0800, Jason Wang wrote:
>>> On 2019/10/23 ??6:11, Tiwei Bie wrote:
>>>> On Wed, Oct 23, 2019 at 03:25:00PM +0800, Jason Wang wrote:
>>>>> On 2019/10/23 ??3:07, Tiwei Bie wrote:
>>>>>> On Wed, Oct 23, 2019 at
2019 Oct 24
0
[PATCH v2] vhost: introduce mdev based hardware backend
...reuse MM of its owner.
We already have VHOST_SET_OWNER in vhost now, parent can handle
the commands in its .kick_vq() which is called by vq's .handle_kick
callback. Virtio-user did something similar:
https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322
>
>
> > But is there any chance to use DMA address? I'm asking since the API
> > then tends to be device specific.
>
>
> I wonder whether we can introduce MAP IOMMU notifier and get DMA mappings
> from that.
I think this will complicate things unn...
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
...> We already have VHOST_SET_OWNER in vhost now, parent can handle
> the commands in its .kick_vq() which is called by vq's .handle_kick
> callback. Virtio-user did something similar:
>
> https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322
This probably means a process context is required, something like
kthread that is used by vhost which seems a burden for parent. Or we can
extend ioctl to processing kick in the system call context.
>
>>
>>> But is there any chance to use DMA address? I'm ask...
2019 Oct 24
2
[PATCH v2] vhost: introduce mdev based hardware backend
...> We already have VHOST_SET_OWNER in vhost now, parent can handle
> the commands in its .kick_vq() which is called by vq's .handle_kick
> callback. Virtio-user did something similar:
>
> https://github.com/DPDK/dpdk/blob/0da7f445df445630c794897347ee360d6fe6348b/drivers/net/virtio/virtio_user_ethdev.c#L313-L322
This probably means a process context is required, something like
kthread that is used by vhost which seems a burden for parent. Or we can
extend ioctl to processing kick in the system call context.
>
>>
>>> But is there any chance to use DMA address? I'm ask...