Searched hist:"48 ce31789834ace5279a97d2f18ea247c9389da4" (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/dev/nvme/ |
| H A D | nvme_private.h | diff 48ce31789834ace5279a97d2f18ea247c9389da4 Tue Mar 26 21:32:57 CET 2013 Jim Harris <jimharris@FreeBSD.org> By default, always escalate to controller reset when an I/O times out.
While aborts are typically cleaner than a full controller reset, many times
an I/O timeout indicates other controller-level issues where aborts may not
work. NVMe drivers for other operating systems are also defaulting to
controller reset rather than aborts for timed out I/O.
Sponsored by: Intel
Reviewed by: carl
|
| H A D | nvme_qpair.c | diff 48ce31789834ace5279a97d2f18ea247c9389da4 Tue Mar 26 21:32:57 CET 2013 Jim Harris <jimharris@FreeBSD.org> By default, always escalate to controller reset when an I/O times out.
While aborts are typically cleaner than a full controller reset, many times
an I/O timeout indicates other controller-level issues where aborts may not
work. NVMe drivers for other operating systems are also defaulting to
controller reset rather than aborts for timed out I/O.
Sponsored by: Intel
Reviewed by: carl
|
| H A D | nvme_ctrlr.c | diff 48ce31789834ace5279a97d2f18ea247c9389da4 Tue Mar 26 21:32:57 CET 2013 Jim Harris <jimharris@FreeBSD.org> By default, always escalate to controller reset when an I/O times out.
While aborts are typically cleaner than a full controller reset, many times
an I/O timeout indicates other controller-level issues where aborts may not
work. NVMe drivers for other operating systems are also defaulting to
controller reset rather than aborts for timed out I/O.
Sponsored by: Intel
Reviewed by: carl
|