search for: skbuffs

Displaying 20 results from an estimated 303 matches for "skbuffs".

2013 Oct 31
6
[PATCH net-next 1/2] net: introduce skb_coalesce_rx_frag()
Sometimes we need to coalesce the rx frags to avoid frag list. One example is virtio-net driver which tries to use small frags for both MTU sized packet and GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Michael Dalton <mwdalton at google.com> Cc: Eric Dumazet
2013 Oct 31
6
[PATCH net-next 1/2] net: introduce skb_coalesce_rx_frag()
Sometimes we need to coalesce the rx frags to avoid frag list. One example is virtio-net driver which tries to use small frags for both MTU sized packet and GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Michael Dalton <mwdalton at google.com> Cc: Eric Dumazet
2013 Oct 31
4
[PATCH net-next V2 1/2] net: introduce skb_coalesce_rx_frag()
Sometimes we need to coalesce the rx frags to avoid frag list. One example is virtio-net driver which tries to use small frags for both MTU sized packet and GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Michael Dalton <mwdalton at google.com> Cc: Eric Dumazet
2013 Oct 31
4
[PATCH net-next V2 1/2] net: introduce skb_coalesce_rx_frag()
Sometimes we need to coalesce the rx frags to avoid frag list. One example is virtio-net driver which tries to use small frags for both MTU sized packet and GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael S. Tsirkin <mst at redhat.com> Cc: Michael Dalton <mwdalton at google.com> Cc: Eric Dumazet
2023 Mar 09
0
[RFC PATCH v3 0/4] several updates to virtio/vsock
On Thu, Mar 09, 2023 at 07:20:20PM +0300, Arseniy Krasnov wrote: > > >On 09.03.2023 19:21, Stefano Garzarella wrote: >> On Thu, Mar 09, 2023 at 01:10:36PM +0300, Arseniy Krasnov wrote: >>> Hello, >>> >>> this patchset evolved from previous v2 version (see link below). It does >>> several updates to virtio/vsock: >>> 1) Changes
2013 Oct 31
0
[PATCH net-next 1/2] net: introduce skb_coalesce_rx_frag()
On 10/31/2013 07:05 PM, Kmindg G wrote: > On Thu, Oct 31, 2013 at 6:28 PM, Jason Wang <jasowang at redhat.com> wrote: >> > Sometimes we need to coalesce the rx frags to avoid frag list. One example is >> > virtio-net driver which tries to use small frags for both MTU sized packet and >> > GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this.
2013 Oct 31
0
[PATCH net-next 1/2] net: introduce skb_coalesce_rx_frag()
On Thu, Oct 31, 2013 at 6:28 PM, Jason Wang <jasowang at redhat.com> wrote: > Sometimes we need to coalesce the rx frags to avoid frag list. One example is > virtio-net driver which tries to use small frags for both MTU sized packet and > GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. > > Cc: Rusty Russell <rusty at rustcorp.com.au> > Cc:
2013 Oct 31
0
[PATCH net-next 1/2] net: introduce skb_coalesce_rx_frag()
On Thu, Oct 31, 2013 at 6:28 PM, Jason Wang <jasowang at redhat.com> wrote: > Sometimes we need to coalesce the rx frags to avoid frag list. One example is > virtio-net driver which tries to use small frags for both MTU sized packet and > GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. > > Cc: Rusty Russell <rusty at rustcorp.com.au> > Cc:
2013 Oct 31
0
[PATCH net-next V2 1/2] net: introduce skb_coalesce_rx_frag()
On Thu, 2013-10-31 at 19:47 +0800, Jason Wang wrote: > Sometimes we need to coalesce the rx frags to avoid frag list. One example is > virtio-net driver which tries to use small frags for both MTU sized packet and > GSO packet. So this patch introduce skb_coalesce_rx_frag() to do this. > > Cc: Rusty Russell <rusty at rustcorp.com.au> > Cc: Michael S. Tsirkin <mst at
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > If the IPv6 fragment id has not been set and we perform > fragmentation due to UFO, select a new fragment id. > When we store the fragment id into skb_shinfo, set the bit > in the skb so we can re-use the selected id. > This preserves the behavior of UFO packets generated on the > host and solves the issue of id
2023 Mar 20
0
[RFC PATCH v1 3/3] test/vsock: skbuff merging test
On Sun, Mar 19, 2023 at 09:53:54PM +0300, Arseniy Krasnov wrote: >This adds test which checks case when data of newly received skbuff is >appended to the last skbuff in the socket's queue. > >This test is actual only for virtio transport. > >Signed-off-by: Arseniy Krasnov <AVKrasnov at sberdevices.ru> >--- > tools/testing/vsock/vsock_test.c | 81
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > > > If the IPv6 fragment id has not been set and we perform > > > fragmentation due to UFO, select a new fragment id. > > > When we store the fragment id into skb_shinfo,
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > > On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > > > If the IPv6 fragment id has not been set and we perform > > > fragmentation due to UFO, select a new fragment id. > > > When we store the fragment id into skb_shinfo,
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote: > On 01/27/2015 08:47 AM, Hannes Frederic Sowa wrote: > > On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > >> On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > >>> On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > >>>> If the IPv6 fragment id has not been set
2015 Jan 27
3
[PATCH 1/3] ipv6: Select fragment id during UFO/GSO segmentation if not set.
On Di, 2015-01-27 at 09:26 -0500, Vlad Yasevich wrote: > On 01/27/2015 08:47 AM, Hannes Frederic Sowa wrote: > > On Di, 2015-01-27 at 10:42 +0200, Michael S. Tsirkin wrote: > >> On Tue, Jan 27, 2015 at 02:47:54AM +0000, Ben Hutchings wrote: > >>> On Mon, 2015-01-26 at 09:37 -0500, Vladislav Yasevich wrote: > >>>> If the IPv6 fragment id has not been set
2014 Dec 17
1
[PATCH 01/10] core: Split out UFO6 support
On Wed, 2014-12-17 at 13:20 -0500, Vladislav Yasevich wrote: > Split IPv6 support for UFO into its own feature similiar to TSO. > This will later allow us to re-enable UFO support for virtio-net > devices. [...] > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h > index 6c8b6f6..8538b67 100644 > --- a/include/linux/skbuff.h > +++ b/include/linux/skbuff.h > @@
2014 Dec 17
1
[PATCH 01/10] core: Split out UFO6 support
On Wed, 2014-12-17 at 13:20 -0500, Vladislav Yasevich wrote: > Split IPv6 support for UFO into its own feature similiar to TSO. > This will later allow us to re-enable UFO support for virtio-net > devices. [...] > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h > index 6c8b6f6..8538b67 100644 > --- a/include/linux/skbuff.h > +++ b/include/linux/skbuff.h > @@
2023 Mar 21
0
[RFC PATCH v3] virtio/vsock: allocate multiple skbuffs on tx
On Tue, Mar 21, 2023 at 12:31:48AM +0300, Arseniy Krasnov wrote: >This adds small optimization for tx path: instead of allocating single >skbuff on every call to transport, allocate multiple skbuff's until >credit space allows, thus trying to send as much as possible data without >return to af_vsock.c. > >Signed-off-by: Arseniy Krasnov <AVKrasnov at sberdevices.ru>
2012 Oct 31
8
[PATCHv2 net-next 0/8] enable/disable zero copy tx dynamically
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b, however you can only enable this mode if you know your workload does not trigger heavy guest to host/host to guest traffic - otherwise you get a (minor) performance regression. This patchset addresses this problem by notifying the owner device when callback is invoked because of a data copy. This makes it possible to