Displaying 13 results from an estimated 13 matches for "virtskb_send".
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...eive_mergeable(struct virtskb *vs, ...);
int virtskb_add_recvbuf_small(struct virtskb*vs, ...);
int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
For the Guest->Host path it should be easier, so maybe I can add a
"virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
of xmit_skb().
Let me know if you have in mind better names or if I should put these function
in another place.
I would like to leave the control part completely separate, so, for example,
the two drivers will negotiate the fe...
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...eive_mergeable(struct virtskb *vs, ...);
int virtskb_add_recvbuf_small(struct virtskb*vs, ...);
int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
For the Guest->Host path it should be easier, so maybe I can add a
"virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
of xmit_skb().
Let me know if you have in mind better names or if I should put these function
in another place.
I would like to leave the control part completely separate, so, for example,
the two drivers will negotiate the fe...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...ecvbuf_big(struct virtskb *vs, ...);
> > > > > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > > > > >
> > > > > > For the Guest->Host path it should be easier, so maybe I can add a
> > > > > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > > > > of xmit_skb().
> > > > >
> > > > > I may miss something, but I don't see any thing that prevents us from using
> > > > > xmit_skb() directly.
> &...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...ecvbuf_big(struct virtskb *vs, ...);
> > > > > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > > > > >
> > > > > > For the Guest->Host path it should be easier, so maybe I can add a
> > > > > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > > > > of xmit_skb().
> > > > >
> > > > > I may miss something, but I don't see any thing that prevents us from using
> > > > > xmit_skb() directly.
> &...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...rtskb_add_recvbuf_small(struct virtskb*vs, ...);
> > int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> >
> > For the Guest->Host path it should be easier, so maybe I can add a
> > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > of xmit_skb().
>
>
> I may miss something, but I don't see any thing that prevents us from using
> xmit_skb() directly.
>
Yes, but my initial idea was to make it more parametric and not related t...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...rtskb_add_recvbuf_small(struct virtskb*vs, ...);
> > int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> >
> > For the Guest->Host path it should be easier, so maybe I can add a
> > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > of xmit_skb().
>
>
> I may miss something, but I don't see any thing that prevents us from using
> xmit_skb() directly.
>
Yes, but my initial idea was to make it more parametric and not related t...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...dd_recvbuf_big(struct virtskb *vs, ...);
>>>>>>> int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
>>>>>>>
>>>>>>> For the Guest->Host path it should be easier, so maybe I can add a
>>>>>>> "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
>>>>>>> of xmit_skb().
>>>>>> I may miss something, but I don't see any thing that prevents us from using
>>>>>> xmit_skb() directly.
>>>>>>
>>...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
.....);
>
> int virtskb_add_recvbuf_small(struct virtskb*vs, ...);
> int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
>
> For the Guest->Host path it should be easier, so maybe I can add a
> "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> of xmit_skb().
I may miss something, but I don't see any thing that prevents us from
using xmit_skb() directly.
>
> Let me know if you have in mind better names or if I should put these function
> in anoth...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt; > > > int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> > > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > > >
> > > > For the Guest->Host path it should be easier, so maybe I can add a
> > > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > > of xmit_skb().
> > >
> > >
> > > I may miss something, but I don't see any thing that prevents us from using
> > > xmit_skb() directly.
> > >
> >
>...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt; > > > int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> > > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > > >
> > > > For the Guest->Host path it should be easier, so maybe I can add a
> > > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > > of xmit_skb().
> > >
> > >
> > > I may miss something, but I don't see any thing that prevents us from using
> > > xmit_skb() directly.
> > >
> >
>...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...truct virtskb*vs, ...);
> > > int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
> > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > >
> > > For the Guest->Host path it should be easier, so maybe I can add a
> > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > of xmit_skb().
> >
> >
> > I may miss something, but I don't see any thing that prevents us from using
> > xmit_skb() directly.
> >
>
> Yes, but my initial idea was to m...
2019 Jul 12
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...;>>> int virtskb_add_recvbuf_big(struct virtskb *vs, ...);
>>>>> int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
>>>>>
>>>>> For the Guest->Host path it should be easier, so maybe I can add a
>>>>> "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
>>>>> of xmit_skb().
>>>>
>>>> I may miss something, but I don't see any thing that prevents us from using
>>>> xmit_skb() directly.
>>>>
>>> Yes, but m...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...rtskb *vs, ...);
> > > > > > > int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
> > > > > > >
> > > > > > > For the Guest->Host path it should be easier, so maybe I can add a
> > > > > > > "virtskb_send(struct virtskb *vs, struct sk_buff *skb)" with a part of the code
> > > > > > > of xmit_skb().
> > > > > >
> > > > > > I may miss something, but I don't see any thing that prevents us from using
> > > > > > xmit_sk...