Re: IOKit Threading?
Re: IOKit Threading?
- Subject: Re: IOKit Threading?
- From: Michael Smith <email@hidden>
- Date: Sat, 3 Mar 2007 18:03:53 -0800
On Mar 3, 2007, at 11:36 AM, Rick Langschultz wrote:
Is it a good idea in my KEXT to utilize threading. I want to be
able to process multiple requests inside the KEXT binary at one
time. Though there will be little to no user notification or
interaction the KEXT must be stable enough to a spawn multiple
client processes and interact with an optional command line utility
which can control the data throughput of the KEXT binary.
It depends a lot on what your extension, is doing, but you managed to
set off several alarm bells with what you've said above.
What do you mean by "utilise threading"?
Kexts do not "a spawn multiple client processes". Did you cut and
paste some of that from another document perhaps? What do you really
mean here?
Typically kexts provide or participate in the provision of services
to clients inside or outside the kernel. It is quite common to
receive concurrent service requests. These tend to arrive either as
arguments to a procedure call, in which case you get a thread with
them for free, or as message events in which case it is up to you to
decide how you want to handle the message queue.
So to a certain extent you must be aware of thread-related issues,
even if you chose to serialise some or all of your extension's work.
Perhaps if you were to describe your objectives in a little more
detail, we could respond with a couple of rough designs that might
reflect the degree of thread-related work you might be faced with.
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden