I want to get back to the (not so) old discussion about this patch: http://www.mail-archive.com/bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx/msg00895.html At the end of the discussion David Miller rejected this Li's patch with such arguments: http://www.mail-archive.com/bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx/msg00907.html DM>Because as Stephen showed it didn't handle all cases. DM>Look at the patch I posted, that's the way to go. David's patch can be viewed here: http://www.mail-archive.com/bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx/msg00902.html I want to revive the discussion with such objections: 1) Yes, the Li's patch doesn't handle all cases, but it handle the obvious case of locally generated packets. Why should bridge-master interface reserve less space then needed by one of its ports? As for me it is naturally for bridge-master reserve the maximum required headroom to match requirements of all its ports. This patch was not intended to handle all cases, only the "locally generated packets" one... 2) The David's patch dynamically computes the needed space for bridged (not locally generated) packets. So, these two patches are not mutually exclusive. I'd rather say, they complement each other. So, I vote for the Li's patch to be reviewed again. I should say that I encountered similar case where bridged port's driver needs more headroom than ETH_HLEN, and this patch saves me cpu cycles from unnecessary skb reallocation (in most cases). Signed-off-by: Li Yang <leoli at freescale.com> --- Use the maximum hard_header_len of ports for bridging device diff -ur a/net/bridge/br_if.c b/net/bridge/br_if.c --- a/net/bridge/br_if.c 2009-05-27 21:15:49.000000000 +0300 +++ b/net/bridge/br_if.c 2009-05-27 21:15:32.000000000 +0300 @@ -344,12 +344,16 @@ { struct net_bridge_port *p; unsigned long features; + unsigned short max_hard_header_len = ETH_HLEN; features = br->feature_mask; list_for_each_entry(p, &br->port_list, list) { features = netdev_compute_features(features, p->dev->features); + if (p->dev->hard_header_len > max_hard_header_len) + max_hard_header_len = p->dev->hard_header_len; } + br->dev->hard_header_len = max_hard_header_len; br->dev->features = features; } -- With Best Regards, Vitaly Demyanec _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
