Re: Question regarding SNACK and bidi transfers

["Mallikarjun C." <cbm@rose.hp.com>]

Section 2.2.2.3 of rev13 currently says the following, which seems the right
place for specifying this. 

"For bidirectional commands, the target uses the DataSN/R2TSN to sequence
Data-In and R2T PDUs in one continuous sequence (undifferentiated)."
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668 
Roseville CA 95747
cbm@rose.hp.com


----- Original Message ----- 
From: "Eddy Quicksall" <eddy_quicksall@ivivity.com>
To: <julian_satran@il.ibm.com>
Cc: <ips@ece.cmu.edu>; "Bill Studenmund" <wrstuden@wasabisystems.com>
Sent: Wednesday, June 19, 2002 3:11 AM
Subject: RE: Question regarding SNACK and bidi transfers


> Julo,
> 
> Since the answer to the 2nd question is "yes" (see your EMAIL with subject
> "Emailing: msg10874.txt"), then I think the spec should make that more clear
> in sections 9.8.1 and 9.7.
> 
> Perhaps in section 9.8.1, it should say something like "Except, when used
> with a bidirectional command and SNACK is being supported, the R2TSN must
> start with a number that couples the R2TSN and DataSN together as one
> continuous sequence". And a similar statement added to 9.7.
> 
> Eddy
> 
> -----Original Message-----
> From: Bill Studenmund [mailto:wrstuden@wasabisystems.com]
> Sent: Tuesday, June 18, 2002 7:56 PM
> To: ips@ece.cmu.edu
> Subject: Question regarding SNACK and bidi transfers
> 
> 
> I have a question about SNACK type 0 requests. In the text, they are
> described as being for Data-In PDUs or R2T PDUs.
> 
> For a bidi command, how do you know which? Does this mean that for a bidi
> command, data-in and R2TSNs have to be mutually-unique (i.e. drawn from
> the same pool)?
> 
> Take care,
> 
> Bill
>