RE: iSCSI: Flow Control

[Michael Krause <krause@cup.hp.com>]

At 07:00 PM 10/3/00 -0700, Jim McGrath wrote:

>The mapping may be a bit trickier.  If the host side manages resources (like
>buffers) on a per connection basis, then that should be the level.  The
>other dimension is time.  Storage traffic is bur sty, so the time span for
>resetting the resource levels should be within the scope of a "burst time"
>or "burst cycle".  This is probably seconds, or perhaps minutes, but not
>hours.  How long would we expect a session to last?  (The problem with
>previous efforts was it was tied into device/host login, which could last
>for days).

A session's duration is a function of the operation being performed so I 
don't think there is any way to quantify to a "best" value either for a 
minimum or a maximum (don't really want to track this within an 
implementation other than what is the current resource).  Burst times are 
also a function of the type of operation being supported - some data base 
queries or large data set (e.g. technical applications) processing can be 
very storage intensive for many hours at a time.  As such, the login 
mechanism is a nice initialization point but the dynamic mechanism needs to 
be present to deal with "real-life" operations which are not steady state 
activities.

I don't see people objecting to this requirement so is this something that 
can be viewed as consensus?

Mike