site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On May 5, 2005, at 8:48 AM, chas williams - CONTRACTOR wrote: how about access to kernel_flock? i suspect one will need to get the kernel funnel if you are going to issue a selwakeup(). -josh _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com In message <36FDEF53-009B-4106-8570-0C1F7913EDC4@apple.com>,Jim Magee writes: Now that we have discovered a couple of drivers that could otherwise be KPI-conforming if not for this, we will be creating a KPI to allocate a selinfo structure dynamically. In the meantime, you can just allocate memory large to be safe. Future versions of selinfo will be smaller than the current one. But to be safe. at least doubling the size of the current selinfo struct should suffice (to say 64 bytes). You should have no reason to look inside the structure. The kernel_flock was part of the old split funnel. The funnels are gone. You are responsible for locking your own data structures. The kernel uses a variety of locks to protect it's own internal data structures. any plans for making a kpi version of net_add_domain and net_add_proto? There are no plans at this time for net_add_domain and net_add_proto. We are interested in hearing about what you might need such functionality for. smime.p7s