Re: [PATCH] Re: IP_MAX_MEMBERSHIPS story.

2006-05-17 Thread Stephen Clark
Bruce M Simpson wrote: On Sun, May 14, 2006 at 03:00:44PM +0100, Bruce M Simpson wrote: So I will be updating the patch in the next 24 hours. Given that it seems stable for values 2047 <= n <= 4095 with SOCK_DGRAM I am inclined to commit with the maximum raised to 4095 and lazy allocation in

Re: [PATCH] Re: IP_MAX_MEMBERSHIPS story.

2006-05-14 Thread Bruce M Simpson
On Sun, May 14, 2006 at 03:00:44PM +0100, Bruce M Simpson wrote: > So I will be updating the patch in the next 24 hours. Given that it > seems stable for values 2047 <= n <= 4095 with SOCK_DGRAM I am inclined > to commit with the maximum raised to 4095 and lazy allocation in place. Committed on HE

Re: [PATCH] Re: IP_MAX_MEMBERSHIPS story.

2006-05-14 Thread Bruce M Simpson
Hello, On Sat, May 13, 2006 at 08:40:30PM -0400, Stephen Clark wrote: > Thanks for your effort - I will try it on monday at work in a test > configuration I have setup with > a hundred gre/vpn tunnels and ospf. This configuration needs a > multicast membership group > of 100. Thank you! I have

Re: [PATCH] Re: IP_MAX_MEMBERSHIPS story.

2006-05-13 Thread Stephen Clark
Bruce M Simpson wrote: Hello, On Fri, May 12, 2006 at 02:12:27PM +0100, Bruce M Simpson wrote: Therefore, joining the same group 20 times on different interfaces would exceed IP_MAX_MEMBERSHIPS. Fixing this in any way would still break the ip_mroute_kmod ABI and as such is a HEAD change.