Displaying 11 results from an estimated 11 matches for "vring_packed_desc_f_write".
2018 Dec 07
0
[RFC 3/3] virtio_ring: use new vring flags
...st struct vring_virtqueue *vq,
flags = state->flags;
- if (flags & VRING_DESC_F_INDIRECT) {
+ if (flags & BIT(VRING_PACKED_DESC_F_INDIRECT)) {
dma_unmap_single(vring_dma_dev(vq),
state->addr, state->len,
- (flags & VRING_DESC_F_WRITE) ?
+ (flags & BIT(VRING_PACKED_DESC_F_WRITE)) ?
DMA_FROM_DEVICE : DMA_TO_DEVICE);
} else {
dma_unmap_page(vring_dma_dev(vq),
state->addr, state->len,
- (flags & VRING_DESC_F_WRITE) ?
+ (flags & BIT(VRING_PACKED_DESC_F_WRITE)) ?
DMA_FROM_DEVICE : DMA_TO_DEVICE);
}
}
@@ -935,1...
2018 Dec 07
7
[RFC 0/3] virtio_ring: define flags as shifts consistently
This is a follow up of the discussion in this thread:
https://patchwork.ozlabs.org/patch/1001015/#2042353
Tiwei Bie (3):
virtio_ring: define flags as shifts consistently
virtio_ring: add VIRTIO_RING_NO_LEGACY
virtio_ring: use new vring flags
drivers/virtio/virtio_ring.c | 100 ++++++++++++++++++-------------
include/uapi/linux/virtio_ring.h | 61 +++++++++++++------
2 files changed,
2018 Dec 07
7
[RFC 0/3] virtio_ring: define flags as shifts consistently
This is a follow up of the discussion in this thread:
https://patchwork.ozlabs.org/patch/1001015/#2042353
Tiwei Bie (3):
virtio_ring: define flags as shifts consistently
virtio_ring: add VIRTIO_RING_NO_LEGACY
virtio_ring: use new vring flags
drivers/virtio/virtio_ring.c | 100 ++++++++++++++++++-------------
include/uapi/linux/virtio_ring.h | 61 +++++++++++++------
2 files changed,
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...O_NOTIFY 0
#define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
or
#define VRING_SPLIT_DESC_F_NEXT 0
#define VRING_SPLIT_DESC_F_WRITE 1
#define VRING_SPLIT_DESC_F_INDIRECT 2
#define VRING_SPLIT_USED_F_NO_NOTIFY 0
#define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
#define VRING_PACKED_DESC_F_NEXT 0
#define VRING_PACKED_DESC_F_WRITE 1
#define VRING_PACKED_DESC_F_INDIRECT 2
>
>
>
> > >
> > >
> > > > >
> > > > >
> > > > > > + */
> > > > > > +#define VRING_PACKED_DESC_F_AVAIL 7
> > > > > > +#define VRING_PACKED...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...O_NOTIFY 0
#define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
or
#define VRING_SPLIT_DESC_F_NEXT 0
#define VRING_SPLIT_DESC_F_WRITE 1
#define VRING_SPLIT_DESC_F_INDIRECT 2
#define VRING_SPLIT_USED_F_NO_NOTIFY 0
#define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
#define VRING_PACKED_DESC_F_NEXT 0
#define VRING_PACKED_DESC_F_WRITE 1
#define VRING_PACKED_DESC_F_INDIRECT 2
>
>
>
> > >
> > >
> > > > >
> > > > >
> > > > > > + */
> > > > > > +#define VRING_PACKED_DESC_F_AVAIL 7
> > > > > > +#define VRING_PACKED...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...DESC_F_NEXT 0
> > #define VRING_SPLIT_DESC_F_WRITE 1
> > #define VRING_SPLIT_DESC_F_INDIRECT 2
> >
> > #define VRING_SPLIT_USED_F_NO_NOTIFY 0
> > #define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
> >
> > #define VRING_PACKED_DESC_F_NEXT 0
> > #define VRING_PACKED_DESC_F_WRITE 1
> > #define VRING_PACKED_DESC_F_INDIRECT 2
>
> As we aren't sharing code I think I prefer the second form.
> Maybe add VRING_NO_LEGACY so people can audit their code
> for assumptions?
Maybe it's better to name it as VIRTIO_RING_NO_LEGACY
which is more consistent wit...
2018 Nov 30
2
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...DESC_F_NEXT 0
> > #define VRING_SPLIT_DESC_F_WRITE 1
> > #define VRING_SPLIT_DESC_F_INDIRECT 2
> >
> > #define VRING_SPLIT_USED_F_NO_NOTIFY 0
> > #define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
> >
> > #define VRING_PACKED_DESC_F_NEXT 0
> > #define VRING_PACKED_DESC_F_WRITE 1
> > #define VRING_PACKED_DESC_F_INDIRECT 2
>
> As we aren't sharing code I think I prefer the second form.
> Maybe add VRING_NO_LEGACY so people can audit their code
> for assumptions?
Maybe it's better to name it as VIRTIO_RING_NO_LEGACY
which is more consistent wit...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...> or
>
> #define VRING_SPLIT_DESC_F_NEXT 0
> #define VRING_SPLIT_DESC_F_WRITE 1
> #define VRING_SPLIT_DESC_F_INDIRECT 2
>
> #define VRING_SPLIT_USED_F_NO_NOTIFY 0
> #define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
>
> #define VRING_PACKED_DESC_F_NEXT 0
> #define VRING_PACKED_DESC_F_WRITE 1
> #define VRING_PACKED_DESC_F_INDIRECT 2
As we aren't sharing code I think I prefer the second form.
Maybe add VRING_NO_LEGACY so people can audit their code
for assumptions?
We also want to guard layout definitions at the end of that file
I think.
> >
> >
> >
>...
2018 Nov 30
0
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
...RING_SPLIT_DESC_F_WRITE 1
> > > #define VRING_SPLIT_DESC_F_INDIRECT 2
> > >
> > > #define VRING_SPLIT_USED_F_NO_NOTIFY 0
> > > #define VRING_SPLIT_AVAIL_F_NO_INTERRUPT 0
> > >
> > > #define VRING_PACKED_DESC_F_NEXT 0
> > > #define VRING_PACKED_DESC_F_WRITE 1
> > > #define VRING_PACKED_DESC_F_INDIRECT 2
> >
> > As we aren't sharing code I think I prefer the second form.
> > Maybe add VRING_NO_LEGACY so people can audit their code
> > for assumptions?
>
> Maybe it's better to name it as VIRTIO_RING_NO_...
2018 Nov 30
4
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
On 2018/11/21 ??6:03, Tiwei Bie wrote:
> Add types and macros for packed ring.
>
> Signed-off-by: Tiwei Bie <tiwei.bie at intel.com>
> ---
> include/uapi/linux/virtio_config.h | 3 +++
> include/uapi/linux/virtio_ring.h | 52 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 55 insertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h
2018 Nov 30
4
[PATCH net-next v3 01/13] virtio: add packed ring types and macros
On 2018/11/21 ??6:03, Tiwei Bie wrote:
> Add types and macros for packed ring.
>
> Signed-off-by: Tiwei Bie <tiwei.bie at intel.com>
> ---
> include/uapi/linux/virtio_config.h | 3 +++
> include/uapi/linux/virtio_ring.h | 52 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 55 insertions(+)
>
> diff --git a/include/uapi/linux/virtio_config.h