Hi Andreas, Thanks for the heads up! There has been big progress on it. It was ratified as a NVMe 1.3 standard in Oct 31st, 2016 in NVMe org(As you may already understand it was ratified as SCSI standard in T10 in May, 2015). The standard compliant product is available for NVMe and SAS in the market. Also Jens Axboe implemented the features in Kernel, etc. We are more than happy to update the status in the meeting. Also it would be a great time to revive the Linux Kernel implementation discussion to support both application-assigned stream ID and kernel-assigned stream ID at the same time. I think people will start circulating the possible approaches sooner or later unless it is already started. Thanks, Changho [resend to include other relevant lists] On Jan 6, 2017, at 4:54 PM, Andreas Dilger <adilger@xxxxxxxxx> wrote: > > At LSF/MM'16 and Linux FAST (https://lwn.net/Articles/685499/) there > were discussions about adding stream IDs to the block/device layer to > allow higher layers (filesystems, applications) to identify IO streams > so lower layers (SSDs, hybrid storage, etc.) can make better allocation/placement decisions. > > It would be useful to get an update on the state of this work, and > discuss any obstacles that need to be resolved for getting this code landed. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
