search for: virtskb_receive_small

Displaying 13 results from an estimated 13 matches for "virtskb_receive_small".

2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...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(struct virtskb *vs, ...); int virtskb_a...
2019 Jul 10
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...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(struct virtskb *vs, ...); int virtskb_a...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...truct receive_queue or > > > > struct send_queue, and some device attributes (e.g. hdr_len ). > > > If you reuse skb or virtnet_info, there is not necessary. > Okay. > > > > > > > > > > > > > > > > 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...
2019 Jul 15
4
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...truct receive_queue or > > > > struct send_queue, and some device attributes (e.g. hdr_len ). > > > If you reuse skb or virtnet_info, there is not necessary. > Okay. > > > > > > > > > > > > > > > > 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...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...> 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 ). > > > > > > 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_r...
2019 Jul 11
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...> 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 ). > > > > > > 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_r...
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, ...); >>>>>>> >>>>>>> int vi...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...e 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_mergeable(struct virtskb *vs, ...); > > int virtskb_add_recvbuf_small(struct virtskb*vs, ...); > int virtskb_add_recvbuf_big(struct virtskb...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt; > 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 ). > > > > > > > > > > > > > > > > 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...
2019 Jul 12
2
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...gt; > 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 ). > > > > > > > > > > > > > > > > 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...
2019 Jul 11
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...rtskb? 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 ). > > > > > > > > > > > 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, ...); > > &g...
2019 Jul 12
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...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 ). If you reuse skb or virtnet_info, there is not necessary. >>> >>>> >>>>> 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 virt...
2019 Jul 15
0
[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock
...queue, and some device attributes (e.g. hdr_len ). > > > > > > If you reuse skb or virtnet_info, there is not necessary. > > > > Okay. > > > > > > > > > > > > > > > > > > > > > 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, ...); > > > > > > > > > > > >...