Displaying 13 results from an estimated 13 matches for "virtskb".
Did you mean:
virt_mb
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...io-net driver), but I think it is feasible.
The idea is to create a virtio-skb.[h,c] where put these functions and a new
object where stores some attributes needed (e.g. hdr_len ) and status (e.g.
some fields of struct receive_queue). This is an idea of virtio-skb.h that
I have in mind:
struct virtskb;
struct sk_buff *virtskb_receive_small(struct virtskb *vs, ...);
struct sk_buff *virtskb_receive_big(struct virtskb *vs, ...);
struct sk_buff *virtskb_receive_mergeable(struct virtskb *vs, ...);
int virtskb_add_recvbuf_small(struct virtskb*vs, ...);
int virtskb_add_recvbuf_big...
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...io-net driver), but I think it is feasible.
The idea is to create a virtio-skb.[h,c] where put these functions and a new
object where stores some attributes needed (e.g. hdr_len ) and status (e.g.
some fields of struct receive_queue). This is an idea of virtio-skb.h that
I have in mind:
struct virtskb;
struct sk_buff *virtskb_receive_small(struct virtskb *vs, ...);
struct sk_buff *virtskb_receive_big(struct virtskb *vs, ...);
struct sk_buff *virtskb_receive_mergeable(struct virtskb *vs, ...);
int virtskb_add_recvbuf_small(struct virtskb*vs, ...);
int virtskb_add_recvbuf_big...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t precludes the compatibility with old hosts. This
was one of the major doubts that made me think about using only the
send/recv skbuff functions, that it shouldn't break the compatibility.
>
> > This is an idea of virtio-skb.h that
> > I have in mind:
> > struct virtskb;
>
>
> What fields do you want to store in virtskb? It looks to be exist sk_buff is
> flexible enough to us?
My idea is to store queues information, like struct receive_queue or
struct send_queue, and some device attributes (e.g. hdr_len ).
>
>
> >
> > stru...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t precludes the compatibility with old hosts. This
was one of the major doubts that made me think about using only the
send/recv skbuff functions, that it shouldn't break the compatibility.
>
> > This is an idea of virtio-skb.h that
> > I have in mind:
> > struct virtskb;
>
>
> What fields do you want to store in virtskb? It looks to be exist sk_buff is
> flexible enough to us?
My idea is to store queues information, like struct receive_queue or
struct send_queue, and some device attributes (e.g. hdr_len ).
>
>
> >
> > stru...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt;
>
> We can extend the current vnet header helper for it to work for vsock.
Okay, I'll do it.
>
>
> > > >
> > > > > > This is an idea of virtio-skb.h that
> > > > > > I have in mind:
> > > > > > struct virtskb;
> > > > >
> > > > > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > > > > flexible enough to us?
> > > > My idea is to store queues information, like struct receive_queue or
> > > > struct send_q...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt;
>
> We can extend the current vnet header helper for it to work for vsock.
Okay, I'll do it.
>
>
> > > >
> > > > > > This is an idea of virtio-skb.h that
> > > > > > I have in mind:
> > > > > > struct virtskb;
> > > > >
> > > > > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > > > > flexible enough to us?
> > > > My idea is to store queues information, like struct receive_queue or
> > > > struct send_q...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...uld be more ambitious here. Do you see any
blocker for reusing virtio-net directly? It's better to reuse not only
the functions but also the logic like NAPI to avoid re-inventing
something buggy and duplicated.
> This is an idea of virtio-skb.h that
> I have in mind:
> struct virtskb;
What fields do you want to store in virtskb? It looks to be exist
sk_buff is flexible enough to us?
>
> struct sk_buff *virtskb_receive_small(struct virtskb *vs, ...);
> struct sk_buff *virtskb_receive_big(struct virtskb *vs, ...);
> struct sk_buff *virtskb_receive_...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...of the major doubts that made me think about using only the
> > send/recv skbuff functions, that it shouldn't break the compatibility.
> >
> > >
> > > > This is an idea of virtio-skb.h that
> > > > I have in mind:
> > > > struct virtskb;
> > >
> > >
> > > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > > flexible enough to us?
> >
> > My idea is to store queues information, like struct receive_queue or
> > struct send_queue, and some device a...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...of the major doubts that made me think about using only the
> > send/recv skbuff functions, that it shouldn't break the compatibility.
> >
> > >
> > > > This is an idea of virtio-skb.h that
> > > > I have in mind:
> > > > struct virtskb;
> > >
> > >
> > > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > > flexible enough to us?
> >
> > My idea is to store queues information, like struct receive_queue or
> > struct send_queue, and some device a...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
>>>>>>> struct sk_buff *virtskb_receive_small(struct virtskb *vs, ...);
>>>>>>> struct sk_buff *virtskb_receive_big(struct virtskb *vs, ...);
>>>>>>> struct sk_buff *virtskb_receive_mergeable(struct virtskb *vs, ...);
>>>>>>>
>>>>>>>...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...old hosts. This
> was one of the major doubts that made me think about using only the
> send/recv skbuff functions, that it shouldn't break the compatibility.
>
> >
> > > This is an idea of virtio-skb.h that
> > > I have in mind:
> > > struct virtskb;
> >
> >
> > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > flexible enough to us?
>
> My idea is to store queues information, like struct receive_queue or
> struct send_queue, and some device attributes (e.g. hdr_len ).
>
&g...
2019 Jul 12
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...> send/recv skbuff functions, that it shouldn't break the compatibility.
We can extend the current vnet header helper for it to work for vsock.
>>>
>>>>> This is an idea of virtio-skb.h that
>>>>> I have in mind:
>>>>> struct virtskb;
>>>>
>>>> What fields do you want to store in virtskb? It looks to be exist sk_buff is
>>>> flexible enough to us?
>>> My idea is to store queues information, like struct receive_queue or
>>> struct send_queue, and some device attributes (e.g....
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t header helper for it to work for vsock.
>
> Okay, I'll do it.
>
> >
> >
> > > > >
> > > > > > > This is an idea of virtio-skb.h that
> > > > > > > I have in mind:
> > > > > > > struct virtskb;
> > > > > >
> > > > > > What fields do you want to store in virtskb? It looks to be exist sk_buff is
> > > > > > flexible enough to us?
> > > > > My idea is to store queues information, like struct receive_queue or
> > >...