It tested well with hyper-v virtual disk. Tested-by: Long Li <[email protected]>
> -----Original Message----- > From: [email protected] [mailto:linux-scsi- > [email protected]] On Behalf Of Andrew Patterson > Sent: Wednesday, June 1, 2016 2:57 PM > To: Christoph Hellwig <[email protected]>; Martin K. Petersen > <[email protected]> > Cc: [email protected]; [email protected] > Subject: Re: [PATCH] sd: Fix rw_max for devices that report an optimal xfer > size > > On 06/01/2016 01:52 AM, Christoph Hellwig wrote: > > Looks fine, > > > > Reviewed-by: Christoph Hellwig <[email protected]> > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-scsi" > > in the body of a message to [email protected] More > majordomo > > info at > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fvger.k > > ernel.org%2fmajordomo- > info.html&data=01%7c01%7clongli%40microsoft.com% > > > 7c424f9a9645da456fa38d08d38a68db13%7c72f988bf86f141af91ab2d7cd011db > 47% > > 7c1&sdata=cojfwxQ8%2bZLpkiT5mFlsclG6DDLBWPk8qNAg3crPtIc%3d > > > > I tested this patch on a 3Par array (32K optimal transfer length) that has > issues without this patch. After applying this patch on a linux-stable kernel, > optimal_io_size is correctly reported as 32K. > > Tested-by: Andrew Patterson <[email protected]> > > -- > Andrew Patterson > Hewlett-Packard Enterprise > -- > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the > body of a message to [email protected] More majordomo info at > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fvger.ker > nel.org%2fmajordomo- > info.html&data=01%7c01%7clongli%40microsoft.com%7c424f9a9645da456fa3 > 8d08d38a68db13%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=cojfwx > Q8%2bZLpkiT5mFlsclG6DDLBWPk8qNAg3crPtIc%3d -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
