Re: timeout for R2T PDUs?
"Deva Ranganathan" <[email protected]> Thu, 6 Nov 2008 14:49:51 +0530
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
--===============1417519460== Content-Type: multipart/alternative; boundary="----=_Part_23435_32276753.1225963191766" ------=_Part_23435_32276753.1225963191766 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan <[email protected] > wrote: > Erez, > > I think that this s a target implementation issue wherein the > implementation can choose the timeout depending on the availability of > resources and the software architecture. A target also has a NOP-IN sent > periodically and can use this to cleanup the stale resources as well. > > thanks > > Deva > HCL Technologies. > > > > On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <[email protected]>wrote: > >> Hi, >> >> I couldn't find an answer to the following question in iSCSI spec: >> >> During the execution of a WRITE command, an R2T PDU is sent from the >> target to the initiator. What should happen if a bug in the initiator >> causes it not to send the data-out PDU? Is there any timeout that will >> allow the target to abort this command? >> >> Thanks, >> Erez >> _______________________________________________ >> Ips mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/ips >> > > ------=_Part_23435_32276753.1225963191766 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <br><br> <div class="gmail_quote">On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan <span dir="ltr"><<a href="mailto:[email protected]">[email protected]</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div>Erez,</div> <div> </div> <div>I think that this s a target implementation issue wherein the implementation can choose the timeout depending on the availability of resources and the software architecture. A target also has a NOP-IN sent periodically and can use this to cleanup the stale resources as well.</div> <div> </div> <div>thanks</div> <div> </div> <div>Deva</div> <div>HCL Technologies.</div> <div> <div></div> <div class="Wj3C7c"> <div><br><br> </div> <div class="gmail_quote">On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <span dir="ltr"><<a href="mailto:[email protected]" target="_blank">[email protected]</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>I couldn't find an answer to the following question in iSCSI spec:<br><br>During the execution of a WRITE command, an R2T PDU is sent from the<br> target to the initiator. What should happen if a bug in the initiator<br>causes it not to send the data-out PDU? Is there any timeout that will<br>allow the target to abort this command?<br><br>Thanks,<br>Erez<br>_______________________________________________<br> Ips mailing list<br><a href="mailto:[email protected]" target="_blank">[email protected]</a><br><a href="https://www.ietf.org/mailman/listinfo/ips" target="_blank">https://www.ietf.org/mailman/listinfo/ips</a><br></blockquote></div> <br></div></div></blockquote></div><br> ------=_Part_23435_32276753.1225963191766-- --===============1417519460== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ips mailing list [email protected] https://www.ietf.org/mailman/listinfo/ips --===============1417519460==--