Re: efficient driver/driver communication
Re: efficient driver/driver communication
- Subject: Re: efficient driver/driver communication
- From: Godfrey van der Linden <email@hidden>
- Date: Mon, 21 Jul 2008 11:15:14 +1000
Again it comes down to how the two drivers are related? Are they
client/provider or superclass/subclass or just totally random
drivers. How do you rendezvous the two drivers?
Godfrey
On 2008-07-21, at 10:10 , Larry Emdur wrote:
Yes, these are both IOKit drivers. Both drivers are mine and I can
share headers. The KEXTs would be separate binaries. I assume it still
safe to pass pointers around in this case, but what is the "fastest"
way to do pass the pointers around?
Laz.
On Sun, Jul 20, 2008 at 4:01 PM, Godfrey van der Linden
<email@hidden> wrote:
You are going to have to give us more context!
What is the driver environment you are running in? I assume IOKit.
Are both drivers yours? Do you have a provider/client connection?
Can you
include headers between the two kexts? Do they live in the same
binary?
What is the memory going to be used for?
The message/messageClient code is mainly used to call a subroutine
in client
driver from a provider.
Finally within the kernel every thing lives in the same address
space so you
don't have to copy data you can just pass pointers.
Godfrey
On 2008-07-19, at 4:53 , Larry Emdur wrote:
What is the most efficient way of moving data between two kexts?
Are the IOService message/messageClient calls the recommended way
to do
this? Do they involve memcpy?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden