lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 29 Jun 2007 14:48:26 +0200 From: Patrick McHardy <kaber@...sh.net> To: Johannes Berg <johannes@...solutions.net> CC: hadi@...erus.ca, Zhang Rui <rui.zhang@...el.com>, netdev@...r.kernel.org, "linux-acpi@...r" <linux-acpi@...r.kernel.org>, lenb@...nel.org, Thomas Graf <tgraf@...g.ch> Subject: Re: Fwd: [PATCH] [-mm] ACPI: export ACPI events via netlink Johannes Berg wrote: > On Fri, 2007-06-29 at 13:51 +0200, Patrick McHardy wrote: > > >>Do multicast groups have to have a seperate name? Or would it suffice >>to have them associated with the genl family and be able to find out >>the starting group number? In that case something like >> >>struct genl_mc_groups { >> struct genl_family *family or char *family_name or similar; >> unsigned int group_off; >> unsigned int group_num; >> unsigned long groups[]; >>}; >> >>seems to make more sense since you only need a single struct >>per family. > > > Hmm, another thought: since we have 32 bits for group numbers and 16 > bits for families we could just reserve 16 bits for groups within each > family. Or do we get trouble with that because in some place there's a > group bitmap or such? Yes, af_netlink has a bitmap per socket that is subscribed to any group. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists