Displaying 16 results from an estimated 16 matches for "add_recvbuf_".
Did you mean:
add_rec_buf
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...have similar challenges (mergeable buffers, page allocation, small
> packets, etc.).
>
> Initially, I would add the skbuff in the virtio-vsock in order to re-use
> receive_*() functions.
Yes, that will be a good step.
> Then I would move receive_[small, big, mergeable]() and
> add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> XDP part on the virtio-net driver), but I think it is feasible.
>
> The idea is to create a virtio-skb.[h,c] where put these functions a...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t 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(struct virtskb *vs, ...);
>>>>>>> int virtskb_add_recvbuf_mergeable(struct virtskb *vs, ...);
>>>>>>>
>>>>>>> For the Guest->Host pa...
2019 Jul 16
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
On Tue, Jul 16, 2019 at 11:40:24AM +0200, Stefano Garzarella wrote:
> On Mon, Jul 15, 2019 at 01:50:28PM -0400, Michael S. Tsirkin wrote:
> > On Mon, Jul 15, 2019 at 09:44:16AM +0200, Stefano Garzarella wrote:
> > > On Fri, Jul 12, 2019 at 06:14:39PM +0800, Jason Wang wrote:
>
> [...]
>
> > > >
> > > >
> > > > I think it's just
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...can reuse some parts also in the virtio-vsock driver, since we
have similar challenges (mergeable buffers, page allocation, small
packets, etc.).
Initially, I would add the skbuff in the virtio-vsock in order to re-use
receive_*() functions.
Then I would move receive_[small, big, mergeable]() and
add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
XDP part on the virtio-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 whe...
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...can reuse some parts also in the virtio-vsock driver, since we
have similar challenges (mergeable buffers, page allocation, small
packets, etc.).
Initially, I would add the skbuff in the virtio-vsock in order to re-use
receive_*() functions.
Then I would move receive_[small, big, mergeable]() and
add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
XDP part on the virtio-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 whe...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...uff in the virtio-vsock in order to re-use
> > > receive_*() functions.
> >
> >
> > Yes, that will be a good step.
> >
>
> Okay, I'll go on this way.
>
> >
> > > Then I would move receive_[small, big, mergeable]() and
> > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > XDP part on the virtio-net driver), but I think it is feasible.
> > >
> > > The idea is to create a vir...
2019 Jul 12
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...in order to re-use
>>>>> receive_*() functions.
>>>>
>>>> Yes, that will be a good step.
>>>>
>>> Okay, I'll go on this way.
>>>
>>>>> Then I would move receive_[small, big, mergeable]() and
>>>>> add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
>>>>> call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
>>>>> XDP part on the virtio-net driver), but I think it is feasible.
>>>>>
>>>>> The...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...> > > > > > Yes, that will be a good step.
> > > > > >
> > > > > Okay, I'll go on this way.
> > > > >
> > > > > > > Then I would move receive_[small, big, mergeable]() and
> > > > > > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > > > > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > > > > > XDP part on the virtio-net driver), but I think it is feasible.
> > > >...
2019 Jul 16
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
On Mon, Jul 15, 2019 at 01:50:28PM -0400, Michael S. Tsirkin wrote:
> On Mon, Jul 15, 2019 at 09:44:16AM +0200, Stefano Garzarella wrote:
> > On Fri, Jul 12, 2019 at 06:14:39PM +0800, Jason Wang wrote:
[...]
> > >
> > >
> > > I think it's just a branch, for ethernet, go for networking stack. otherwise
> > > go for vsock core?
> > >
2019 Jul 16
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
On Mon, Jul 15, 2019 at 01:50:28PM -0400, Michael S. Tsirkin wrote:
> On Mon, Jul 15, 2019 at 09:44:16AM +0200, Stefano Garzarella wrote:
> > On Fri, Jul 12, 2019 at 06:14:39PM +0800, Jason Wang wrote:
[...]
> > >
> > >
> > > I think it's just a branch, for ethernet, go for networking stack. otherwise
> > > go for vsock core?
> > >
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
....).
> >
> > Initially, I would add the skbuff in the virtio-vsock in order to re-use
> > receive_*() functions.
>
>
> Yes, that will be a good step.
>
Okay, I'll go on this way.
>
> > Then I would move receive_[small, big, mergeable]() and
> > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > XDP part on the virtio-net driver), but I think it is feasible.
> >
> > The idea is to create a virtio-skb.[h,c] where...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
....).
> >
> > Initially, I would add the skbuff in the virtio-vsock in order to re-use
> > receive_*() functions.
>
>
> Yes, that will be a good step.
>
Okay, I'll go on this way.
>
> > Then I would move receive_[small, big, mergeable]() and
> > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > XDP part on the virtio-net driver), but I think it is feasible.
> >
> > The idea is to create a virtio-skb.[h,c] where...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t; > receive_*() functions.
> > >
> > >
> > > Yes, that will be a good step.
> > >
> >
> > Okay, I'll go on this way.
> >
> > >
> > > > Then I would move receive_[small, big, mergeable]() and
> > > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > > XDP part on the virtio-net driver), but I think it is feasible.
> > > >
> > > > The ide...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...t; > receive_*() functions.
> > >
> > >
> > > Yes, that will be a good step.
> > >
> >
> > Okay, I'll go on this way.
> >
> > >
> > > > Then I would move receive_[small, big, mergeable]() and
> > > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > > XDP part on the virtio-net driver), but I think it is feasible.
> > > >
> > > > The ide...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...ns.
> > > > >
> > > > > Yes, that will be a good step.
> > > > >
> > > > Okay, I'll go on this way.
> > > >
> > > > > > Then I would move receive_[small, big, mergeable]() and
> > > > > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > > > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > > > > XDP part on the virtio-net driver), but I think it is feasible.
> > > > > >...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...ns.
> > > > >
> > > > > Yes, that will be a good step.
> > > > >
> > > > Okay, I'll go on this way.
> > > >
> > > > > > Then I would move receive_[small, big, mergeable]() and
> > > > > > add_recvbuf_[small, big, mergeable]() outside of virtio-net driver, in order to
> > > > > > call them also from virtio-vsock. I need to do some refactoring (e.g. leave the
> > > > > > XDP part on the virtio-net driver), but I think it is feasible.
> > > > > >...