Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size
From: Tom Yan <hidden>
Date: 2016-08-14 08:46:01
Also in:
linux-scsi
Possibly related (same subject, not in this thread)
- 2016-08-16 · Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size · "Martin K. Petersen" <martin.petersen@oracle.com>
- 2016-08-12 · Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size · Tom Yan <hidden>
- 2016-08-12 · Re: [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size · "Martin K. Petersen" <martin.petersen@oracle.com>
- 2016-08-11 · [RFC] sd: dynamically adjust SD_MAX_WS16_BLOCKS as per the actual logical block size · <hidden>
On 13 August 2016 at 04:26, Martin K. Petersen [off-list ref] wrote:
quoted
quoted
quoted
quoted
quoted
"Tom" == Tom Yan [off-list ref] writes:Tom, Tom> I don't really follow. What would this BLK_MAX_BIO_SECTORS be? It Tom> doesn't appear to me that a static value is going to address the Tom> problem I am addressing in this patch. 0x7fffff, the maximum number of block layer sectors that can be expressed in a single bio.
Hmm, so when we queue any of the limits, we convert a certain maximum number of physical sectors (which we has already been doing) to its corresponding maximum number of block layer sectors, and then make sure that number does not exceed 0x7fffff, right?
-- Martin K. Petersen Oracle Linux Engineering