openvswitch/datapath/linux-2.6/compat-2.6/skbuff-openvswitch.c

#if !defined(HAVE_SKB_WARN_LRO) && defined(NETIF_F_LRO)

#include <linux/netdevice.h>

void __skb_warn_lro_forwarding(const struct sk_buff *skb)
{
	if (net_ratelimit())
		printk(KERN_WARNING "%s: received packets cannot be forwarded"
				    " while LRO is enabled\n", skb->dev->name);
}

#endif
datapath: Break out test for dev_disable_lro(). It seems that dev_disable_lro() and skb_warn_if_lro() are not always defined at the same time, despite the fact that they are typically used together. This independently tests for them. 2010-05-06 15:15:50 -07:00			`#if !defined(HAVE_SKB_WARN_LRO) && defined(NETIF_F_LRO)`
datapath: Disable large receive offload. LRO can play fast and loose with the packets that it merges, which isn't very polite when you are bridging packets for other operating systems. This disables LRO on any underlying devices that are added to the datapath, which is the same as what the bridge does. Note that this does not disable GRO, which has a more strict set of rules about what is merged and is therefore safe for bridging. Both are typically done in software anyways. 2010-02-19 16:54:19 -05:00
			`#include <linux/netdevice.h>`

			`void __skb_warn_lro_forwarding(const struct sk_buff *skb)`
			`{`
			`if (net_ratelimit())`
			`printk(KERN_WARNING "%s: received packets cannot be forwarded"`
			`" while LRO is enabled\n", skb->dev->name);`
			`}`

datapath: Break out test for dev_disable_lro(). It seems that dev_disable_lro() and skb_warn_if_lro() are not always defined at the same time, despite the fact that they are typically used together. This independently tests for them. 2010-05-06 15:15:50 -07:00			`#endif`