> > What is the target device type ? The one I have seen was HP target, I can't remember if I have seen it on other target though...
> > If a target supports REC, but does not support Sequence retransmission > (i.e., RETRY bit=0 in PRLI response), then it's probably a disk device. It was indeed disk device. > > REC for general usage (i.e., for more devices than just tape) was added a > while ago to allow for polling of the Exchange (i.e., QUERY TASK). > > ...Dave I think the bottom line is no SRR != no REC, even it's not tape, we would still want to do REC to keep tracking the status, which is what we are already doing. Thanks, yi > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Zou, Yi > Sent: Friday, November 12, 2010 2:41 PM > To: [email protected] > Subject: [Open-FCoE] Question regaring REC and SRR in libfc/fc_fcp > > Hi, > I have noticed that in one of my testing where the target supports REC but > does not support RETRY in PRLI reply. In this case, fc_fcp_srr() is never > really sending SRR but just goes to fc_fcp_retry_cmd() directly since > FC_RP_FLAGS_RETRY of the rport is not set. I understand that no RETRY does > not mean no REC from FCP-3 spec, so we can't disable REC because of no > RETRY, but for us, in this case, we got REC accepted, but we are not able > to send SRR, does that mean we want to fail the I/O at that point already? > I am also not sure if it is common for target to support REC but no RETRY. > > Thanks, > yi > > > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel > _______________________________________________ > devel mailing list > [email protected] > http://www.open-fcoe.org/mailman/listinfo/devel _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
