Re: which kind of driver to design for AoE protocol?
- From: "KOOLER" <anton@xxxxxxxxxxxxxxxxxx>
- Date: 19 Aug 2006 01:21:50 -0700
Since there would be nobody between you and your NDIS protocol driver
you may implement private API to handle the requests at raised
interrupt level. In any case you'll be creating "TDI-like" thing so
there's really no need to completely clone TDI (with all it strong and
esp. weak points).
Anton
soviet_bloke@xxxxxxxxxxx писал(а):
Hi Don
This depends, assuming you are planning to use the standard network stack,....
I am afraid you would not get away with the standard network stack
here. If you want to use the existing stack, you have to allocate IRPs
with TdiBuildInternalDeviceControlIrp(), and the above can be done only
at IRQL==PASSIVE_LEVEL, although your port routines may get called at
higher IRQL ( (in fact, you can pre-allocate few IRPs in advance, but
imagine what happens if you run out of your IRP pool and have to send a
request at IRQL>PASSIVE_LEVEL).
Therefore, you have to write a full-fledged NDIS protocol driver (or at
least implement quite advanced form of NDIS hooking), so that this task
is *DEFINITELY* not for someone without any kernel-mode experience
whatsoever
Anton Bassov
Don Burn wrote:
This depends, assuming you are planning to use the standard network stack,
you probably will need a virtual storport driver similar to iSCSI. The
problem here is this is brand new stuff that Microsoft is betaing for some
platforms, so there is little data available. Take a look at the
presentations from WinHEC this year on storage and try contacting the
various email addresses.
This is going to be a big project and something that will be extremely hard
for a newbie to do.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
"Ebola_Influenza" <EbolaInfluenza@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:744B4F21-41B3-4684-97D2-47B4DB2E9E9A@xxxxxxxxxxxxxxxx
Hello all,
I've been asked to look at designing a Windows driver for the AoE (ATA
over
Ethernet) protocol (coraid.com). I've been an applications developer for
eight years now, but never done a driver before.
After reading the MS doc "Getting Started with the Windows Driver
Development Environment", the first and most obvious question is "which
kind
of driver should I build?"
Any and all advice will be appreciated!
Best,
EI
.
- Follow-Ups:
- Re: which kind of driver to design for AoE protocol?
- From: soviet_bloke
- Re: which kind of driver to design for AoE protocol?
- References:
- Re: which kind of driver to design for AoE protocol?
- From: Don Burn
- Re: which kind of driver to design for AoE protocol?
- From: soviet_bloke
- Re: which kind of driver to design for AoE protocol?
- Prev by Date: Re: User mode vs. Kernel mode driver
- Next by Date: Re: which kind of driver to design for AoE protocol?
- Previous by thread: Re: which kind of driver to design for AoE protocol?
- Next by thread: Re: which kind of driver to design for AoE protocol?
- Index(es):
Relevant Pages
|
