Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from newbox.ece.cmu.edu (localhost [127.0.0.1])
	by newbox.ece.cmu.edu (Cyrus v2.1.12) with LMTP; Thu, 31 Jul 2003 21:05:42 -0400
X-Sieve: CMU Sieve 2.2
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by newbox.ece.cmu.edu (Postfix) with ESMTP id 3E7E8323D
	for <ipsml@ece.cmu.edu>; Thu, 31 Jul 2003 21:05:42 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id DD317F7; Thu, 31 Jul 2003 21:05:41 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP
	id 50A9ED6; Thu, 31 Jul 2003 21:05:32 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 01D9989FC; Thu, 31 Jul 2003 21:05:16 -0400 (EDT)
Delivered-To: ips-outgoing@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id DC4AC89F5
	for <ips-outgoing@sos.ece.cmu.edu>; Thu, 31 Jul 2003 21:05:15 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id B53C3D6; Thu, 31 Jul 2003 21:05:15 -0400 (EDT)
Delivered-To: ips-outgoing@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 75AC9B2; Thu, 31 Jul 2003 21:05:15 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id 443B1E3
	for <ips-outgoing@ece.cmu.edu>; Thu, 31 Jul 2003 21:04:53 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 2C6768A1A; Thu, 31 Jul 2003 21:04:53 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Delivered-To: ips@sos.ece.cmu.edu
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 488D889F5
	for <ips@sos.ece.cmu.edu>; Thu, 31 Jul 2003 21:04:51 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id 2B9886A; Thu, 31 Jul 2003 21:04:51 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 002B36F; Thu, 31 Jul 2003 21:04:50 -0400 (EDT)
Received: from thebe.your-site.com (thebe.your-site.com [140.186.45.26])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id 45D326A
	for <ips@ece.cmu.edu>; Thu, 31 Jul 2003 21:04:48 -0400 (EDT)
Received: from asomi.com (64-144-5-25.client.dsl.net [64.144.5.25])
	by thebe.your-site.com (Postfix) with ESMTP
	id 4A44C244BBF; Thu, 31 Jul 2003 21:04:58 -0400 (EDT)
Date: Thu, 31 Jul 2003 20:04:45 -0500
Subject: Re: [rddp] Re: iSCSI/iWARP drafts and flow control
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
Cc: <ips@ece.cmu.edu>, <rddp@ietf.org>
To: "Mallikarjun C." <cbm@rose.hp.com>
From: Caitlin Bestler <cait@asomi.com>
In-Reply-To: <020c01c357c6$0a21e340$18a4f40f@rose.hp.com>
Message-Id: <23D23E30-C3BC-11D7-9DE7-003065D48EE0@asomi.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-29.1 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES,USER_AGENT_APPLEMAIL
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)


On Thursday, July 31, 2003, at 07:43 PM, Mallikarjun C. wrote:

>
>> No new wire protocol is required.
>
> Please explain to me how credit can be replenished
> in the following example - without new positive flow
> control protocol.
>
> An initiator sends an immediate command in an untagged
> message to the target (and thus consumes one "fringe" credit).
>
> Considerations: a) CmdSN is not unique, can't be acked.
> b) target may discard it, or may process it c) no assumptions
> can be made based on  subsequent command processing.
>
> The other specific iSCSI PDU types that I listed present
> a similar "problem" - for both directions.

There are three cases:

-- If there is no need to send a further untagged message
    then there is no need to reclaim the credit.

-- If there is a later need to send a untagged message
    against the "main" credits, then the reply to that
    command will replenish the credits.

-- Only exception: when sending an untagged message that
    requires the last "fringe credit", or when the "main"
    credits have been exhausted, a flag is set requesting
    an explicit flow control ack. Or a flag in the untagged
    message could request such a flow control ack.

In general, responses to the "main" untagged messages
replenish both "main" and "fringe" credits. This can
be done without complex accounting, something along
the lines of a "leaky bucket" algorithm.

If you somehow exceed the "maximum" number of "fringe"
credits without using "main" credits, you an simply
use some form of "nop" command, or have a special
"fringe" command to replenish "fringe" credits.
But if such a a command is actually needed, it would
mean that the sender is sending more "fringe" methods
than the statistical methods would have allowed for
in any event.

Credits do not have to be run at a "as close to zero"
basis as possible in order to qualify as flow control.

You will probably object to having to send a reverse
message "just" to ack the fringe methods. However,
exactly such a message is being generated now at
by TCP. If you really have a sequence of "fringe"
/ "oneway" messages, you are already generating
a TCP segment to ack them. The only difference
is that iSER would supply some data with that
reverse flow TCP segment.

