Re: which kind of driver to design for AoE protocol?

The whole idea of using raw ethernet instead of TCP as a transport is
to make the thing
faster to run. With your vision of incapsulating AoE ethernet frames
inside UDP you'll have everything working 1) dog slow 2) you would not
be compatible with exiting AoE hardware and software targets. The only
benefit you'd have - your own protocol would be IP routable...

Looks like you're not far far away from the original question :)

Anton

soviet_bloke@xxxxxxxxxxx написав:
Hi Maxim

What about implementing AoE over UDP (i.e. more or less the same way
VPN drivers implement PPP over TCP)

How is this possible? This is IIRC Ethernet-based protocol, which is not
compatible with TCP/IP at all. I don't think AoE packets have IP headers, for
instance.

As long as your software is installed on both ends of communication,
there is no problem whatsoever. After all, it does not matter what kind
of transport communicating parties chose - as long as packets reach
their destination there is no problem whatsoever. Therefore, they may
choose UDP as their transport, i.e. wrap their packets into UDP ones
and send them as UDP data. As far as network is concerned, the whole
thing is all about exchanging UDP packets - it has no idea about AoE
whatsoever. Certainly, if your software is installed only on one end of
communication and another endpoint is system-provided, it is not going
to work this way....

Anton Bassov

AoE packets have a meaning only for drivers that actually communicate
over AoE, and
Maxim S. Shatskih wrote:
What about implementing AoE over UDP (i.e. more or less the same way
VPN drivers implement PPP over TCP)

How is this possible? This is IIRC Ethernet-based protocol, which is not
compatible with TCP/IP at all. I don't think AoE packets have IP headers, for
instance.

Don't forget that the OP does not have any kernel-mode experience. In
fact, TDI client
is pretty much the same thing as Winsock (although more cumbersome and
a bit confusing at the first glance - I don't argue about that).

TDI is by far harder to understand and there is no samples.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

.

Relevant Pages