SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    RE: iscsi : default iscsi mode page settings.



    If there's no reasonable default it makes sense to mandate exchange of at
    least this one text key.
    
    Marjorie 
    
    > -----Original Message-----
    > From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
    > Sent: Friday, September 21, 2001 7:58 AM
    > To: ips@ece.cmu.edu
    > Subject: RE: iscsi : default iscsi mode page settings.
    > 
    > 
    > I thought you where concerned about "boot duration"? julo
    > 
    > 
    >                                                               
    >                            
    >                     "KRUEGER,MARJOR                           
    >                            
    >                     IE                    To:     IPS 
    > Reflector <ips@ece.cmu.edu>        
    >                     (HP-Roseville,e       cc:                 
    >                            
    >                     x1)"                  Subject:     RE: 
    > iscsi : default iscsi mode    
    >
    > I vote for making the exchange of some text parameters 
    > MANDATORY, with no
    > defaults.
    > 
    > Marj
    > 
    > > -----Original Message-----
    > > From: Robert Snively [mailto:rsnively@Brocade.COM]
    > > Sent: Thursday, September 20, 2001 10:48 AM
    > > To: 'Sanjeev Bhagat (TRIPACE/Zoetermeer)'; 'Santosh Rao'; IPS
    > > Reflector
    > > Subject: RE: iscsi : default iscsi mode page settings.
    > >
    > >
    > > It is true that default mode settings for Mode Pages
    > > are usually arranged between buyer and vendor for
    > > maximum convenience in the buyer's systems.  It is
    > > generally true that any setting of a Mode Page will
    > > allow the protocol to operate correctly, except a few,
    > > notably the first burst size parameter if
    > > ImmediateData is set to yes.
    > >
    > > On the other hand, some of the iSCSI text keyed
    > > parameters MUST be known before the protocol will
    > > operate correctly.  ImmediateData is certainly
    > > one of those.  As a result, you have two choices:
    > >
    > >    a)   Make the negotiation of all such parameters
    > >    MANDATORY during the login and after any
    > >    reset that may change them,  or;
    > >
    > >    b)   Define a default state that will be guaranteed
    > >    unless and until the parameter has been explicitly
    > >    changed.
    > >
    > > Your choice.
    > >
    > > Bob
    


Home

Last updated: Fri Sep 21 13:17:18 2001
6662 messages in chronological order