search for: dma_mapping

On Thu, Mar 2, 2023 at 7:59?PM Xuan Zhuo <xuanzhuo at linux.alibaba.com> wrote: > > virtqueue_add_split() only supports virtual addresses, dma is completed > in virtqueue_add_split(). > > In some scenarios (such as the AF_XDP scenario), the memory is allocated > and DMA is completed in advance, so it is necessary for us to support > passing the DMA address to virtio

On Tue, 7 Mar 2023 14:43:42 +0800, Jason Wang <jasowang at redhat.com> wrote: > On Thu, Mar 2, 2023 at 7:59?PM Xuan Zhuo <xuanzhuo at linux.alibaba.com> wrote: > > > > virtqueue_add_split() only supports virtual addresses, dma is completed > > in virtqueue_add_split(). > > > > In some scenarios (such as the AF_XDP scenario), the memory is allocated >

XDP socket(AF_XDP) is an excellent bypass kernel network framework. The zero copy feature of xsk (XDP socket) needs to be supported by the driver. The performance of zero copy is very good. ENV: Qemu with vhost. vhost cpu | Guest APP CPU |Guest Softirq CPU | PPS -----------------------------|---------------|------------------|------------ xmit by sockperf: 90% | 100%

On Wed, Aug 16, 2023 at 3:49?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: > > > > On 8/14/2023 7:21 PM, Jason Wang wrote: > > On Tue, Aug 15, 2023 at 9:46?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: > >> Signed-off-by: Si-Wei Liu <si-wei.liu at oracle.com> > >> --- > >> include/linux/vdpa.h | 7 +++++++ > >> 1 file

On 8/17/2023 8:28 AM, Eugenio Perez Martin wrote: > On Thu, Aug 17, 2023 at 2:05?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: >> >> >> On 8/15/2023 6:55 PM, Jason Wang wrote: >>> On Wed, Aug 16, 2023 at 3:49?AM Si-Wei Liu <si-wei.liu at oracle.com> wrote: >>>> >>>> On 8/14/2023 7:21 PM, Jason Wang wrote: >>>>> On

On Wed, Jun 17, 2020 at 11:29:46AM +0800, Jason Wang wrote: > In order to let userspace work correctly, get_iova_range() is a must > for the device that has its own DMA translation logic. I guess you mean for a device. However in absence of ths op, I don't see what is wrong with just assuming device can access any address. > > Signed-off-by: Jason Wang <jasowang at

On Thu, Jun 18, 2020 at 01:56:25PM +0800, Jason Wang wrote: > This patches extend the vhost IOTLB API to accept batch updating hints > form userspace. When userspace wants update the device IOTLB in a > batch, it may do: > > 1) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_BEGIN flag > 2) Perform a batch of IOTLB updating via VHOST_IOTLB_UPDATE/INVALIDATE > 3) Write

On Thu, Jun 18, 2020 at 01:56:25PM +0800, Jason Wang wrote: > This patches extend the vhost IOTLB API to accept batch updating hints > form userspace. When userspace wants update the device IOTLB in a > batch, it may do: > > 1) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_BEGIN flag > 2) Perform a batch of IOTLB updating via VHOST_IOTLB_UPDATE/INVALIDATE > 3) Write

On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: > On 07/12/15 16:19, Stefano Stabellini wrote: > > Hi all, > > > > this patch series introduces support for running Linux on top of Xen > > inside a virtual machine with virtio devices (nested virt scenario). > > The problem is that Linux virtio drivers use virt_to_phys to get the > > guest

On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: > On 07/12/15 16:19, Stefano Stabellini wrote: > > Hi all, > > > > this patch series introduces support for running Linux on top of Xen > > inside a virtual machine with virtio devices (nested virt scenario). > > The problem is that Linux virtio drivers use virt_to_phys to get the > > guest

Hi all, this patch series introduces support for running Linux on top of Xen inside a virtual machine with virtio devices (nested virt scenario). The problem is that Linux virtio drivers use virt_to_phys to get the guest pseudo-physical addresses to pass to the backend, which doesn't work as expected on Xen. Switching the virtio drivers to the dma APIs (dma_alloc_coherent,

Hi all, this patch series introduces support for running Linux on top of Xen inside a virtual machine with virtio devices (nested virt scenario). The problem is that Linux virtio drivers use virt_to_phys to get the guest pseudo-physical addresses to pass to the backend, which doesn't work as expected on Xen. Switching the virtio drivers to the dma APIs (dma_alloc_coherent,

Hi all: This series tries to support batched IOTLB updating vhost-vdpa. Currently vhost-vdpa accepts userspace mapping via IOTLB API, and it can only forward one mapping to IOMMU or device through IOMMU API or dma_map(). Though set_map() is deisgend to have the capability to pass an rbtree based mapping to vDPA device, it's still be called at least once for each VHOST_IOTLB_UPDATE or

On Mon, Jun 29, 2020 at 05:26:03PM +0800, Jason Wang wrote: > > On 2020/6/28 ??5:58, Michael S. Tsirkin wrote: > > On Thu, Jun 18, 2020 at 01:56:25PM +0800, Jason Wang wrote: > > > This patches extend the vhost IOTLB API to accept batch updating hints > > > form userspace. When userspace wants update the device IOTLB in a > > > batch, it may do: > >

Hi all: This series tries to support batched IOTLB updating vhost-vdpa. Currently vhost-vdpa accepts userspace mapping via IOTLB API, and it can only forward one mapping to IOMMU or device through IOMMU API or dma_map(). Though set_map() is designed to have the capability to pass an rbtree based mapping to vDPA device, it's still be called at least once for each VHOST_IOTLB_UPDATE or

On Mon, 14 Dec 2015, Andy Lutomirski wrote: > On Mon, Dec 14, 2015 at 6:12 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: > >> On 07/12/15 16:19, Stefano Stabellini wrote: > >> > Hi all, > >> > > >> > this patch series introduces support for running Linux on top of Xen

On Mon, 14 Dec 2015, Andy Lutomirski wrote: > On Mon, Dec 14, 2015 at 6:12 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: > >> On 07/12/15 16:19, Stefano Stabellini wrote: > >> > Hi all, > >> > > >> > this patch series introduces support for running Linux on top of Xen

This patches extend the vhost IOTLB API to accept batch updating hints form userspace. When userspace wants update the device IOTLB in a batch, it may do: 1) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_BEGIN flag 2) Perform a batch of IOTLB updating via VHOST_IOTLB_UPDATE/INVALIDATE 3) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_END flag Vhost-vdpa may decide to batch the IOMMU/IOTLB updating

On 2020/6/28 ??5:58, Michael S. Tsirkin wrote: > On Thu, Jun 18, 2020 at 01:56:25PM +0800, Jason Wang wrote: >> This patches extend the vhost IOTLB API to accept batch updating hints >> form userspace. When userspace wants update the device IOTLB in a >> batch, it may do: >> >> 1) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_BEGIN flag >> 2) Perform a batch

On Mon, Dec 14, 2015 at 10:27:52AM -0800, Andy Lutomirski wrote: > On Mon, Dec 14, 2015 at 6:12 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Mon, Dec 14, 2015 at 02:00:05PM +0000, David Vrabel wrote: > >> On 07/12/15 16:19, Stefano Stabellini wrote: > >> > Hi all, > >> > > >> > this patch series introduces support for running