Re: profiles - a way to simplify iSCSI

["Matt Wakeley" <matt_wakeley@agilent.com>]

The whole purpose for creating iSCSI in the first place (by the group that
started it) was to create a storage interconnect that could take advantage of
the very high performance promised by 10GBE, at low cost.  Mutliple
connections per session is there to take advantage of the 10GBE link with the
shortcomings of TCP, and markers are there to eliminate the cost of memory
subsystems required to buffer out of order TCP frames.  Eliminate these, and
you've you'll capitulate to Fibre Channel for anything but slow storage
connects.

-Matt

John Vrabel wrote:
> 
> > It's time to start thinking about what we can take out ...
> 
> I fully agree with the need to limit options, and avoid the need for
> profiles.
> 
> FWIW, our list of things to remove:
> 
>      1) Markers
> 
>      2) SNACKs
> 
>      3) Command retries
> 
>      4) Async Messages
> 
>      5) Multiple connections per session
> 
> Things to change:
> 
>      1) default number of connections from 8 to 1 ( if multiple connections
> remain )
> 
>  Things I'm less sure about:
> 
>      1) InitialR2T, ImmediateData.  Do they really need to be negotiable?
>          FirstBurstSize  controls them to a great extent.
>          Can InitialR2T be removed, and retain ImmediateData for short
> writes ?
> 
> John Vrabel