USB Attached SCSI

UAS is defined across two standards, the T10 "USB Attached SCSI" (T10/2095-D) referred to as the "UAS" specification, and the USB "Universal Serial Bus Mass Storage ClassUSB Attached SCSI Protocol (UASP)" specification. The T10 technical committee of the International Committee for Information Technology Standards (INCITS) develops and maintains the UAS specification; the SCSI Trade Association (SCSITA) promotes the UAS technology. The USB mass-storage device class (MSC) Working Group develops and maintains the UASP specification; the USB Implementers Forum, Inc. (USB-IF) promotes the UASP technology. UAS drivers generally provide faster transfers when compared to the older USB Mass Storage Bulk-Only Transport (BOT) protocol drivers. Although UAS was added in the USB 3.0 standard, it can also be used at USB 2.0 speeds, assuming compatible hardware. When used with an SSD, UAS is considerably faster than BOT for random reads and writes given the same USB transfer rate. The speed of a native SATA 3 interface is 6.0 Gbit/s. When using a USB 3.0 link (5.0 Gbit/s), which is slower than a SATA3 link, the performance is limited by the USB link. However, later USB protocols have higher transfer rates, with USB4 allowing 80 Gbit/s. A UAS drive can be implemented using a SATA3 drive attached through a SATA–UAS bridge with the SATA transfer rate limiting throughput, however, a native UAS SSD can take full advantage of higher USB transfer rates. The original UAS standard (ANSI INCITS 471-2010 and ISO/IEC 14776-251:2014) can be referred to as UAS-1. A UAS-2 project was started by T10 but cancelled. That effort was resurrected as UAS-3, which is now a published standard (INCITS 572-2021). Apart from being based on later versions of other SCSI standards (e.g. SAM-6 and SPC-6, both under development) the technical author described the changes between UAS-1 and UAS-3 as follows: "allow the device to switch data transfers from one command to another before the current command is complete". == Hardware support ==

USB controller/hub In July 2010 SemiAccurate reported that Gigabyte Technology had introduced working UAS drivers for their hardware using NEC/Renesas chips. The same Renesas UAS driver (for Windows) also works with AMD's A70M and A75 Fusion Controller Hubs, the USB part of which was co-developed by AMD and Renesas. In October 2011, ASMedia USB controllers chips had gained driver support as well (they had support on the hardware side before). As for support by Intel Platform Controller Hub (PCH), an article in MyCE notes: "The native Intel USB3 UASP solution is only supported under Windows 8. To further complicate matters, not all Z77 motherboards support USB3 UASP. A license is required to implement UASP, and not all motherboard manufacturers are prepared to pass on the extra cost of this license to the end user." A few Allwinner Technology SoCs feature UAS support over USB 2.0 in Linux. Storage devices Of USB–SATA bridges, "the LucidPort USB300 and USB302, Symwave SW6315, Texas Instruments TUSB9261 and the VLI VL700 controllers all support UASP, while the ASMedia ASM1051 and ASM1051E as well as the Fujitsu MB86C30A doesn't." ASMedia 1053-s and 1153 support UAS. offers full USB 3.2 UAS performance, reaching data transfer speeds of up to 2 Gbyte/s. == Operating system support ==

Microsoft added native support for UAS to Windows 8. Drives supporting UAS load Uaspstor.sys instead of the older Usbstor.sys. Windows 8 supports UAS by default over USB 2.0 as well. UAS drivers and products are certified by Microsoft using the Windows Hardware Certification Kit. Apple added native support for UAS to OS X 10.8 Mountain Lion; drives using UAS show up in System Information → Software → Extensions as IOUSBAttachedSCSI (or IOUSBMassStorageUASDriver, depending on the version of OS X) "Loaded: Yes". Drives listed with "Loaded: No" are defaulting to the older, slower Bulk Only Transport (BOT) mode. This may occur if the drive's USB controller, the Mac's USB port, or any attached USB hub doesn't support UASP mode. The Linux kernel has supported UAS since 8 June 2014 when the version 3.15 was released. However, some distributions of Linux such as Ubuntu (from v11.xx onwards) have reported issues with some misbehaving hardware. The kernel has a built-in blocklist for devices with "quirks" defined in . Temporary additional quirks can be added via procfs or kernel command line (). FreeBSD does not support UAS as of August 2018. On older operating systems that do not support UAS class, a UAS device may be run in USB Mass Storage Bulk-Only Transport mode for compatibility. == Goals ==

• Designed to directly address the failings of the USB mass-storage device class bulk-only transports (BOT) • Enables command queuing and out-of-order completions for USB mass-storage devices • Eliminates software overhead for SCSI command phases • Enables TRIM (UNMAP in SCSI terminology) operation for SSDs • Up to 64K commands may be queued • SCSI Architectural Model (SAM-4) compliant • USB 3.0 SuperSpeed and USB 2.0 High-Speed versions defined • USB 3.0 SuperSpeed – host controller (xHCI) hardware support, no software overhead for out-of-order commands • USB 2.0 High-speed – enables command queuing in USB 2.0 drives • Streams were added to the USB 3.0 SuperSpeed protocol for supporting UAS out-of-order completions • USB 3.0 host controller (xHCI) provides hardware support for streams == See also ==