Re: Storage over Ethernet/IP

[Karl Auerbach]

 
> a.  TCP is too CPU intensive and creates too much latency for storage I/O operations.
> 
> b.  The IP stack is too top heavy and processing packet headers is too
> slow to support storage I/O operations.

There were some papers published duing the late '80's or early '90s by
John Romkey and I belive Dave Clark and Van Jacobson about the length of
instruction sequences to handle TCP.  I'm not sure that those ever became
RFCs.

Those papers came up with figures indicating that if one structures code
"correctly" and if the net path is "clean" (i.e. not a lot of packet loss,
reordering, replication, etc) than the per-packet instruction sequences
(sans IP checksum calculation) were potantially very short.

Does anyone have the references to these papers?

                --karl--