David Miller wrote:
The kernel supports much more than 32 groups, see nlk->groups which is
a bitmap which can be sized to arbitrary sizes. nlk->nl_groups is
for backwards compatability only.
netlink_change_ngroups() does the bitmap resizing when necessary.
Thanks for the explanation. Given that it's a bitmap doesn't that
result in a cost of O(number of groups) when processing messages? In
our case we need potentially thousands of groups.
The root multicast listening restriction can be relaxed in some
circumstances, whatever is needed to fill your needs.
Also, good to know.
Stop making excuses, with minor adjustments we have the facilities to
meet your needs. There is no need for yet-another-protocol to do what
you're trying to do, we already have too much duplicated
functionality.
You may have confused me with the OP...I just chimed in because of some
of the limitations we found when we wanted to do similar things. In our
case we created a new unix-like protocol to allow multicast, and have
been using it for a few years.
However, if we could use netlink instead in our next release that would
be a good thing. A couple questions:
1) Is it possible to register to receive all netlink messages for a
particular netlink family? This is useful for debugging--it allows a
tcpdump equivalent.
2) Is there any up-to-date netlink programming guide? I found this one:
http://people.redhat.com/nhorman/papers/netlink.pdf
but it's three years old now.
Thanks,
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
