Displaying 12 results from an estimated 12 matches for "virtio_net_f_hdr_gso_udp".
2014 Dec 24
2
[PATCH 00/10] Split UFO into v4 and v6 versions.
...o continue to support legacy guests that assume that UFO6
> > support included into UFO(4).
> >
> > Without this work, migrating a guest to a 3.18 kernel fails.
> >
>
> This series eliminate the ambiguous NETIF_F_UFO.
>
> But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
> ambigious. I know it was used to keep compatibility for legacy guest. But
> what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
> gso type in vnet header looks sufficient?
[...]
The IPv6 fragmentation ID needs to be added to the vnet header, to do
U...
2014 Dec 24
2
[PATCH 00/10] Split UFO into v4 and v6 versions.
...o continue to support legacy guests that assume that UFO6
> > support included into UFO(4).
> >
> > Without this work, migrating a guest to a 3.18 kernel fails.
> >
>
> This series eliminate the ambiguous NETIF_F_UFO.
>
> But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
> ambigious. I know it was used to keep compatibility for legacy guest. But
> what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
> gso type in vnet header looks sufficient?
[...]
The IPv6 fragmentation ID needs to be added to the vnet header, to do
U...
2014 Dec 25
2
[PATCH 00/10] Split UFO into v4 and v6 versions.
...pport included into UFO(4).
>> > >
>> > > Without this work, migrating a guest to a 3.18 kernel fails.
>> > >
>> >
>> > This series eliminate the ambiguous NETIF_F_UFO.
>> >
>> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is
>> still
>> > ambigious. I know it was used to keep compatibility for legacy
>> guest. But
>> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio
>> features and
>> > gso type in vnet header looks sufficient?
>> [...]
&g...
2014 Dec 25
2
[PATCH 00/10] Split UFO into v4 and v6 versions.
...pport included into UFO(4).
>> > >
>> > > Without this work, migrating a guest to a 3.18 kernel fails.
>> > >
>> >
>> > This series eliminate the ambiguous NETIF_F_UFO.
>> >
>> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is
>> still
>> > ambigious. I know it was used to keep compatibility for legacy
>> guest. But
>> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio
>> features and
>> > gso type in vnet header looks sufficient?
>> [...]
&g...
2014 Dec 18
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...IPv4 performance for guests.
> We also continue to support legacy guests that assume that UFO6
> support included into UFO(4).
>
> Without this work, migrating a guest to a 3.18 kernel fails.
>
This series eliminate the ambiguous NETIF_F_UFO.
But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
ambigious. I know it was used to keep compatibility for legacy guest. But
what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
gso type in vnet header looks sufficient?
With the series, we can't send UFOv6 packet but legacy guest can. How about
fix the UFOv...
2014 Dec 24
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...assume that UFO6
> > > support included into UFO(4).
> > >
> > > Without this work, migrating a guest to a 3.18 kernel fails.
> > >
> >
> > This series eliminate the ambiguous NETIF_F_UFO.
> >
> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
> > ambigious. I know it was used to keep compatibility for legacy guest. But
> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
> > gso type in vnet header looks sufficient?
> [...]
>
> The IPv6 fragmentation ID needs to be add...
2014 Dec 18
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...IPv4 performance for guests.
> We also continue to support legacy guests that assume that UFO6
> support included into UFO(4).
>
> Without this work, migrating a guest to a 3.18 kernel fails.
>
This series eliminate the ambiguous NETIF_F_UFO.
But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
ambigious. I know it was used to keep compatibility for legacy guest. But
what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
gso type in vnet header looks sufficient?
With the series, we can't send UFOv6 packet but legacy guest can. How about
fix the UFOv...
2014 Dec 24
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...assume that UFO6
> > > support included into UFO(4).
> > >
> > > Without this work, migrating a guest to a 3.18 kernel fails.
> > >
> >
> > This series eliminate the ambiguous NETIF_F_UFO.
> >
> > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is still
> > ambigious. I know it was used to keep compatibility for legacy guest. But
> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio features and
> > gso type in vnet header looks sufficient?
> [...]
>
> The IPv6 fragmentation ID needs to be add...
2014 Dec 25
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...6
> >> > > support included into UFO(4).
> >> > > > > Without this work, migrating a guest to a 3.18 kernel fails.
> >> > > > > This series eliminate the ambiguous NETIF_F_UFO.
> >> > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is
> >>still
> >> > ambigious. I know it was used to keep compatibility for legacy guest.
> >>But
> >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio
> >>features and
> >> > gso type in vnet header looks sufficien...
2014 Dec 25
0
[PATCH 00/10] Split UFO into v4 and v6 versions.
...6
> >> > > support included into UFO(4).
> >> > > > > Without this work, migrating a guest to a 3.18 kernel fails.
> >> > > > > This series eliminate the ambiguous NETIF_F_UFO.
> >> > > But VIRTIO_NET_F_{HOST|GUEST}_UFO and VIRTIO_NET_F_HDR_GSO_UDP is
> >>still
> >> > ambigious. I know it was used to keep compatibility for legacy guest.
> >>But
> >> > what's the future plan? Differentiate UFOv4 and UFOv6 in virtio
> >>features and
> >> > gso type in vnet header looks sufficien...
2014 Dec 17
20
[PATCH 00/10] Split UFO into v4 and v6 versions.
UFO support in the kernel applies to both IPv4 and IPv6 protocols
with the same device feature. However some devices may not be able
to support one of the offloads. For this we split the UFO offload
feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and
this series introduces NETIF_F_UFO6.
As a result of this work, we can now re-enable NETIF_F_UFO on
virtio_net devices and restore
2014 Dec 17
20
[PATCH 00/10] Split UFO into v4 and v6 versions.
UFO support in the kernel applies to both IPv4 and IPv6 protocols
with the same device feature. However some devices may not be able
to support one of the offloads. For this we split the UFO offload
feature into 2 pieces. NETIF_F_UFO now controlls the IPv4 part and
this series introduces NETIF_F_UFO6.
As a result of this work, we can now re-enable NETIF_F_UFO on
virtio_net devices and restore