summaryrefslogtreecommitdiff
path: root/net/bridge
diff options
context:
space:
mode:
authorSimon Horman <horms@verge.net.au>2010-08-22 17:35:32 +0000
committerDavid S. Miller <davem@davemloft.net>2010-08-22 21:09:04 -0700
commitc2368e795cec561229ef66a04ac51629b918a9e8 (patch)
tree2fd08484e8948dc2969ac2d01b00af175b93abb5 /net/bridge
parentfcb12fd2236f49aa8fdc1568ed4ebdfe4fddc6b5 (diff)
downloadlinux-exynos-c2368e795cec561229ef66a04ac51629b918a9e8.tar.gz
linux-exynos-c2368e795cec561229ef66a04ac51629b918a9e8.tar.bz2
linux-exynos-c2368e795cec561229ef66a04ac51629b918a9e8.zip
bridge: is PACKET_LOOPBACK unlikely()?
While looking at using netdev_rx_handler_register for openvswitch Jesse Gross suggested that an unlikely() might be worthwhile in that code. I'm interested to see if its appropriate for the bridge code. Cc: Jesse Gross <jesse@nicira.com> Signed-off-by: Simon Horman <horms@verge.net.au> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge')
-rw-r--r--net/bridge/br_input.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
index 826cd5221536..6d04cfdf4541 100644
--- a/net/bridge/br_input.c
+++ b/net/bridge/br_input.c
@@ -141,7 +141,7 @@ struct sk_buff *br_handle_frame(struct sk_buff *skb)
const unsigned char *dest = eth_hdr(skb)->h_dest;
int (*rhook)(struct sk_buff *skb);
- if (skb->pkt_type == PACKET_LOOPBACK)
+ if (unlikely(skb->pkt_type == PACKET_LOOPBACK))
return skb;
if (!is_valid_ether_addr(eth_hdr(skb)->h_source))