mir/openvswitch
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-10-07 13:40:45 +00:00
Code Issues Releases Wiki Activity
Files
316078c7252ebca1e12f07928512955077f4ce5f
openvswitch/datapath/linux/compat/skbuff-openvswitch.c

17 lines
373 B
C
Raw Normal View History

gre: Restructure tunneling. Following patch restructures ovs tunneling and gre vport implementation to make ovs tunneling more in sync with upstream kernel tunneling. Doing this tunneling code is simplified as most of protocol processing on send and recv is pushed to kernel tunneling. For external ovs module the code is moved to kernel compatibility code. Signed-off-by: Pravin B Shelar <pshelar@nicira.com> Acked-by: Jesse Gross <jesse@nicira.com>
2013-06-20 17:11:43 -07:00
#include <linux/module.h>
#include <linux/netdevice.h>
#include <linux/skbuff.h>
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
treewide: Use pr_fmt and pr_<level> Signed-off-by: Joe Perches <joe@perches.com> Acked-by: Simon Horman <horms@verge.net.au> [Jesse: Added missing pr_fmt in vport-gre.c and dp_sysfs_dp.c] Signed-off-by: Jesse Gross <jesse@nicira.com>
2010-08-30 00:24:54 -07:00
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
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
void __skb_warn_lro_forwarding(const struct sk_buff *skb)
{
if (net_ratelimit())
treewide: Use pr_fmt and pr_<level> Signed-off-by: Joe Perches <joe@perches.com> Acked-by: Simon Horman <horms@verge.net.au> [Jesse: Added missing pr_fmt in vport-gre.c and dp_sysfs_dp.c] Signed-off-by: Jesse Gross <jesse@nicira.com>
2010-08-30 00:24:54 -07:00
pr_warn("%s: received packets cannot be forwarded while LRO is enabled\n",
skb->dev->name);
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
}
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
Reference in New Issue Copy Permalink