[T10] Should this WRITE STREAM error response be changed?
Amir Dagan1
AMIRDA at il.ibm.com
Tue Nov 15 00:19:01 PST 2016
Could there be a mode page bit to allow for either error handling methods,
depending on the system preferences?
From: Gerry Houlder <gerry.houlder at seagate.com>
To: T10 Reflector <t10 at t10.org>
Date: 2016-11-14 20:03
Subject: [T10] Should this WRITE STREAM error response be changed?
Sent by: t10-bounces at t10.org
Hi,
i received a comment that NVMe Write Stream error handling has a
difference with respect to SAS error handling and there is a request to
make them the same in this regard.
With SAS, if the target device receives a Write Stream command with a
Stream_ID that is not valid then the target is required to reject the
command with CHECK CONDITION and the host has to figure out how it wants
to retry the command.
With NVMe, if the device receives a Write Stream command with a Stream_ID
that is not valid then the device handles the Write Stream command like it
is a regular non-stream write command. This means the Stream_ID is ignored
and the write proceeds normally without the hint of the Stream_ID. This is
recommended as friendlier to the host in that the overhead of handling a
rejected command and retrying the command is avoided.
Should SBC-4 be changed to specify that an invalid Stream_ID is ignored
the the write command proceeds as a non-streaming write command? I'd like
to hears some other opinions (either for or against) before I write a
proposal along these lines._______________________________________________
T10 mailing list
T10 at t10.org
http://www.t10.org/mailman/listinfo/t10
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.t10.org/pipermail/t10/attachments/20161115/32df7890/attachment.html>
More information about the T10
mailing list