SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    RE: iSCSI: Use of the A bit




    That could be so but it would be overkill. Status ACK can implicitly acknowledge the last transfer.
    And Yes the fact that the last transfer is not mentioned is an oversight that I will correct.
    This does not mean that you HAVE TO raise the A flag or that you are ENCOURAGED to do so :-)

    Julo


    Paul Koning <ni1d@arrl.net>
    Sent by: owner-ips@ece.cmu.edu

    15-03-02 16:09
    Please respond to Paul Koning

           
            To:        Eddy_Quicksall@ivivity.com
            cc:        rod.harrison@windriver.com, ips@ece.cmu.edu
            Subject:        RE: iSCSI: Use of the A bit

           


    >>>>> "Eddy" == Eddy Quicksall <Eddy_Quicksall@ivivity.com> writes:

    Eddy> I think we may need better explanation about why some folks
    Eddy> don't want to do the "positive ack".

    >> We got to this position, since so many folks did not want to
    >> support the positive ack.

    Something doesn't compute here.

    I don't believe the discussion has anything to do with whether you
    support positive ACK or not.  If you're doing error recovery level 1
    or above, then you are required to support it, because the other end
    is allowed to say A=1 and you're required to answer that.

    If you don't want to support positive ACK, the solution is to support
    only error recovery level 0.

    The issue under discussion is whether the rule "you are allowed to set
    A=1 only once per MaxBurstSize" is correct.  At this point it's clear
    to me that it is not, because you need to be able to set A=1 at the
    end of the transfer.  The current rule forbids that unless the total
    transfer size is >= MaxBurstSize.

    Kevin's proposal is a simple fix to this problem.

                     paul





Home

Last updated: Sat Mar 16 00:18:05 2002
9145 messages in chronological order