Displaying 20 results from an estimated 5000 matches similar to: "[PATCH v4 08/42] virtio: allow transports to get avail/used addresses"
2014 Oct 23
0
[PATCH RFC v4 08/17] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 23
0
[PATCH RFC v4 08/17] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 24
0
[PATCH v3 07/41] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 27
0
[PATCH v5 10/45] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 24
0
[PATCH v3 07/41] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 27
0
[PATCH v5 10/45] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 27
0
[PATCH v6 11/46] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 30
0
[PATCH v7 11/46] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Dec 01
0
[PATCH v8 11/50] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 27
0
[PATCH v6 11/46] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Nov 30
0
[PATCH v7 11/46] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Dec 01
0
[PATCH v8 11/50] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 22
0
[PATCH RFC v2 08/16] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 22
0
[PATCH RFC v3 08/16] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 22
0
[PATCH RFC v2 08/16] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 22
0
[PATCH RFC v3 08/16] virtio: allow transports to get avail/used addresses
From: Cornelia Huck <cornelia.huck at de.ibm.com>
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the
2014 Oct 07
0
[PATCH RFC 06/11] virtio: allow transports to get avail/used addresses
For virtio-1, we can theoretically have a more complex virtqueue
layout with avail and used buffers not on a contiguous memory area
with the descriptor table. For now, it's fine for a transport driver
to stay with the old layout: It needs, however, a way to access
the locations of the avail/used rings so it can register them with
the host.
Reviewed-by: David Hildenbrand <dahi at
2016 Feb 01
0
[PATCH v6 6/9] virtio: Add improved queue allocation API
This leaves vring_new_virtqueue alone for compatbility, but it
adds two new improved APIs:
vring_create_virtqueue: Creates a virtqueue backed by automatically
allocated coherent memory. (Some day it this could be extended to
support non-coherent memory, too, if there ends up being a platform
on which it's worthwhile.)
__vring_new_virtqueue: Creates a virtqueue with a manually-specified
2016 Feb 02
1
[PATCH v6 6/9] virtio: Add improved queue allocation API
On Mon, Feb 01, 2016 at 10:00:56AM -0800, Andy Lutomirski wrote:
> This leaves vring_new_virtqueue alone for compatbility, but it
> adds two new improved APIs:
>
> vring_create_virtqueue: Creates a virtqueue backed by automatically
> allocated coherent memory. (Some day it this could be extended to
> support non-coherent memory, too, if there ends up being a platform
> on
2016 Feb 02
1
[PATCH v6 6/9] virtio: Add improved queue allocation API
On Mon, Feb 01, 2016 at 10:00:56AM -0800, Andy Lutomirski wrote:
> This leaves vring_new_virtqueue alone for compatbility, but it
> adds two new improved APIs:
>
> vring_create_virtqueue: Creates a virtqueue backed by automatically
> allocated coherent memory. (Some day it this could be extended to
> support non-coherent memory, too, if there ends up being a platform
> on