anton
Sat Jul 24 18:06:14 CDT 2004
Ken,
I think I gave you enough of starting points (source code
availability) in private e-mails and other news groups. Just a few
more advices about iSCSI target design you and some other people maybe
would find costing their paid attention. You should consider avoiding
high-level level stuff as much as you can (no .NET, no MFC, no Winsock
extensions). Stick to pure C or very light-weight C++ (no exceptions,
no RTTI, own overloaded new and delete operators etc). Have own basic
types of fixed length defined (typedef unsigned char Ui8 etc) you'll
be using to describe iSCSI structures. Isolate all API calls in
separate set of wrappers. Have code up and running in user mode under
Win32. Treat this code as a prototype. If you'll have commercial
success (I wish you good luck, there are not so many competitors for
our own free software, LOL) you'll definitely end with porting your
code to other OS. And moving it to kernel of course. If you'll follow
the advices "no need in drivers, user mode code works just great" (c)
do not remember who, you'll end with complete redesign and at least
half a year delay in upcoming kernel version. We've been cought dead
once with this stuff, I'd like you avoiding our mistakes :)
BTW, "no need in drivers, user mode code works just great" is very
close to "640K of memory should be enough to everybody" (c) you all
know who.
Regards,
Anton Kolomyeytsev
CEO, Rocket Division Software
"Ken Allen" <nospamkendrhyd@sympatico.ca> wrote in message news:<egpXrR0bEHA.2544@TK2MSFTNGP10.phx.gbl>...
> Any references on how one would commence such development, and can .Net be
> used for this? I know that there have been some issues getting non-dot-net
> socket code to work with .Net standard interfaces, and I am a bit concerned
> about that. Are there any restrictions on the port or IP addressing,
> especially those used by the Microsoft iSCSI client? Does the Microsoft
> iSCSI client use any 'discovery' tools to determine which iSCSI targets are
> available.
>
> -ken
>
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:eP$dytybEHA.2908@TK2MSFTNGP10.phx.gbl...
> > The target can be well-implemented in user mode, no need in driver
> writing.
> >
> > --
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > maxim@storagecraft.com
> >
http://www.storagecraft.com
> >
> >
> > "Ken Allen" <nospamkendrhyd@sympatico.ca> wrote in message
> > news:ufD6lrybEHA.1000@TK2MSFTNGP12.phx.gbl...
> > > Are there any references to writing an iSCSI target driver for Windows?
> I
> > > understand that Microsoft provides an iSCSI client driver, but we wanted
> to
> > > develop our own iSCSI targe driver for remote devices.
> > >
> > > -ken
> > >
> > > P.S. Any references available for developing the iSCSI target in user
> space
> > > instead of in a driver? That way we could write a service that could
> handle
> > > the iSCSI commands; just need to be able to register as an iSCSI target
> and
> > > receive (and intepret) the protocol).
> > >
> > >
> >
> >