Kernel to non-kernel comms
- From: "Dave Williams" <dont@xxxxxxx>
- Date: Tue, 31 May 2005 12:40:18 +0100
Hi, I'm just starting a project which is going to have a kernel level driver
included, actually an Installable File System mini-driver, but I'm not that
familiar with any issues related to kernel drivers (and I'm sure there are
many).
Specifically, my driver is going to need to talk ultimately to an existing
service through DCOM. My inclination (perhaps unjustified) is to put as
little coding as possible into the kernel driver, to minimise the chance of
problems with it causing a kernel hang. So my thought is to have a 'helper'
application which runs in user mode (perhaps a service) and talks to the
kernel driver, then the helper app can deal with the DCOM calls, and hang if
the RPC call hangs etc without disturbing the kernel.
Is this really necessary, and if so, is there a recommended way that the
components should talk to each other like named pipes or shared memory or
COM - perhaps more specifically, is there anything I should avoid.
Also, any recommendations of websites or books about 'typical pitfalls' with
this stuff would be appreciated.
Thanks,
Dave
.
- Follow-Ups:
- Re: Kernel to non-kernel comms
- From: Slava M. Usov
- Re: Kernel to non-kernel comms
- From: Don Burn
- Re: Kernel to non-kernel comms
- Prev by Date: OT: How to search binary occurences in files
- Next by Date: Re: Kernel to non-kernel comms
- Previous by thread: OT: How to search binary occurences in files
- Next by thread: Re: Kernel to non-kernel comms
- Index(es):
Relevant Pages
|
