Author: rmilecki
Date: 2015-09-08 18:43:10 +0200 (Tue, 08 Sep 2015)
New Revision: 46826

Modified:
   
trunk/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch
   
trunk/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch
   
trunk/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch
Log:
kernel: describe bridge patch "remove IPv6 depependency of bridge in 2.6.38+"

It was initially added in r27237 by jow as patch from Jonas.

Modified: 
trunk/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch
===================================================================
--- 
trunk/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch 
    2015-09-08 16:43:04 UTC (rev 46825)
+++ 
trunk/target/linux/generic/patches-3.18/643-bridge_remove_ipv6_dependency.patch 
    2015-09-08 16:43:10 UTC (rev 46826)
@@ -1,3 +1,16 @@
+From: Jonas Gorski <[email protected]>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
 --- a/include/net/addrconf.h
 +++ b/include/net/addrconf.h
 @@ -88,6 +88,12 @@ int ipv6_rcv_saddr_equal(const struct so

Modified: 
trunk/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch
===================================================================
--- 
trunk/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch  
    2015-09-08 16:43:04 UTC (rev 46825)
+++ 
trunk/target/linux/generic/patches-4.0/643-bridge_remove_ipv6_dependency.patch  
    2015-09-08 16:43:10 UTC (rev 46826)
@@ -1,3 +1,16 @@
+From: Jonas Gorski <[email protected]>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
 --- a/include/net/addrconf.h
 +++ b/include/net/addrconf.h
 @@ -91,6 +91,12 @@ int ipv6_rcv_saddr_equal(const struct so

Modified: 
trunk/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch
===================================================================
--- 
trunk/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch  
    2015-09-08 16:43:04 UTC (rev 46825)
+++ 
trunk/target/linux/generic/patches-4.1/643-bridge_remove_ipv6_dependency.patch  
    2015-09-08 16:43:10 UTC (rev 46826)
@@ -1,3 +1,16 @@
+From: Jonas Gorski <[email protected]>
+Subject: [PATCH] bridge: remove IPv6 depependency of bridge in 2.6.38+
+
+Since 2.6.38 the bridge module has a dependency to IPv6 if IPv6 is
+enabled. Since the IPv6 module isn't exactly lightweight and bridge also
+only needs a single function from IPv6, it's rather easy to create a
+common "lib" module with a RCU pointer to the actual implementation, if
+the IPv6 module is loaded (although slightly hackish).
+
+The codepath seems to be only taken when using IPv6, so there should be
+no negative side effects when IPv6 isn't loaded. I did not measure how
+big the performance impact is.
+---
 --- a/include/net/addrconf.h
 +++ b/include/net/addrconf.h
 @@ -91,6 +91,12 @@ int ipv6_rcv_saddr_equal(const struct so
_______________________________________________
openwrt-commits mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-commits

Reply via email to