[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: iSCSI: DataACK SNACK
- To: "Julian Satran" <Julian_Satran@il.ibm.com>
- Subject: RE: iSCSI: DataACK SNACK
- From: "Chuck Micalizzi" <firstname.lastname@example.org>
- Date: Fri, 15 Feb 2002 13:14:43 -0800
- Cc: <email@example.com>
- content-class: urn:content-classes:message
- Content-Type: multipart/alternative;boundary="----_=_NextPart_001_01C1B665.C966E380"
- Sender: firstname.lastname@example.org
- Thread-Index: AcG2RnwIRcfkHp0PRvi1brIqAU24bgAGdJCQ
- Thread-Topic: iSCSI: DataACK SNACK
Thank you for the response.
Let me try to be more direct. If a target has
been issued multiple
read commands, with transfer counts
that exceed the negotiated
maxBurstSize. After the target sends a data sequence
for one of these
commands must it wait for a DataACK before sending a
for another command. Or is it free to send a data
sequence for each outstanding
If the target can have a data sequence in flight for each
active command then
it must expect a DataACK for each sequence sent with
bit set. If the DataACK SNACK doesn't include a task Tag
the target can't be
certain as to which data sequence the initiator is
acknowledging. So how can
the target determine which resources to free or which
sequence to send next?
DataACK is a "bulk
ack". Answering the last (in case of several) is good enough.
I fail to see your point.
Sent by: email@example.com
Subject: iSCSI: DataACK SNACK
I have a question regarding
Rev. 10 section 10.16.1 states:
For a Data/R2T SNACK, the Initiator Task Tag MUST be set
to the Initiator Task Tag of the referenced Command.
Otherwise, it is reserved.
The DataACK is used to free resources at the
not to request or imply data
Is the target allowed to have more than
outstanding on a connection?
If multiple outstanding DataACKs are allowed per
then in my opinion the DataACK must have a valid
inorder for the target to associate the DataACK with
appropriate resources to be freed.