* [PATCH net v2] ipv4: update comment to document GSO fragmentation cases.
@ 2016-11-09 20:04 Lance Richardson
2016-11-10 17:02 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Lance Richardson @ 2016-11-09 20:04 UTC (permalink / raw)
To: netdev
This is a follow-up to commit 9ee6c5dc816a ("ipv4: allow local
fragmentation in ip_finish_output_gso()"), updating the comment
documenting cases in which fragmentation is needed for egress
GSO packets.
Suggested-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Reviewed-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Signed-off-by: Lance Richardson <lrichard@redhat.com>
---
v2: corrected commit ID (v1 used local commit ID by mistake)
net/ipv4/ip_output.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
index 4971401..c2dae40 100644
--- a/net/ipv4/ip_output.c
+++ b/net/ipv4/ip_output.c
@@ -244,12 +244,18 @@ static int ip_finish_output_gso(struct net *net, struct sock *sk,
if (skb_gso_validate_mtu(skb, mtu))
return ip_finish_output2(net, sk, skb);
- /* Slowpath - GSO segment length is exceeding the dst MTU.
+ /* Slowpath - GSO segment length exceeds the egress MTU.
*
- * This can happen in two cases:
- * 1) TCP GRO packet, DF bit not set
- * 2) skb arrived via virtio-net, we thus get TSO/GSO skbs directly
- * from host network stack.
+ * This can happen in several cases:
+ * - Forwarding of a TCP GRO skb, when DF flag is not set.
+ * - Forwarding of an skb that arrived on a virtualization interface
+ * (virtio-net/vhost/tap) with TSO/GSO size set by other network
+ * stack.
+ * - Local GSO skb transmitted on an NETIF_F_TSO tunnel stacked over an
+ * interface with a smaller MTU.
+ * - Arriving GRO skb (or GSO skb in a virtualized environment) that is
+ * bridged to a NETIF_F_TSO tunnel stacked over an interface with an
+ * insufficent MTU.
*/
features = netif_skb_features(skb);
BUILD_BUG_ON(sizeof(*IPCB(skb)) > SKB_SGO_CB_OFFSET);
--
2.5.5
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH net v2] ipv4: update comment to document GSO fragmentation cases.
2016-11-09 20:04 [PATCH net v2] ipv4: update comment to document GSO fragmentation cases Lance Richardson
@ 2016-11-10 17:02 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2016-11-10 17:02 UTC (permalink / raw)
To: lrichard; +Cc: netdev
From: Lance Richardson <lrichard@redhat.com>
Date: Wed, 9 Nov 2016 15:04:39 -0500
> This is a follow-up to commit 9ee6c5dc816a ("ipv4: allow local
> fragmentation in ip_finish_output_gso()"), updating the comment
> documenting cases in which fragmentation is needed for egress
> GSO packets.
>
> Suggested-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> Reviewed-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> Signed-off-by: Lance Richardson <lrichard@redhat.com>
> ---
> v2: corrected commit ID (v1 used local commit ID by mistake)
Applied.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-11-10 17:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-09 20:04 [PATCH net v2] ipv4: update comment to document GSO fragmentation cases Lance Richardson
2016-11-10 17:02 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox