Thread (1 message) 1 message, 1 author, 2016-08-12

Re: [PATCH v2 2/2] libata-core: do not set dev->max_sectors for LBA48 devices

From: "Martin K. Petersen" <martin.petersen@oracle.com>
Date: 2016-08-12 21:17:43
Also in: linux-block, linux-ide

Possibly related (same subject, not in this thread)

quoted
quoted
quoted
quoted
"Alan" == One Thousand Gnomes [off-list ref] writes:
Alan,

Alan> For older SCSI and especially ATA drives (and it wouldn't surprise
Alan> me if it is true of modern ones) there are also huge latency
Alan> tradeoffs.

Absolutely.

Alan> Before you jump up and down about numbers what are the latency
Alan> numbers like on classic ATA drives with that sized block I/O. You
Alan> could easily up your RAID numbers while wrecking realtime and
Alan> desktop performance.

I was in no way advocating raising the default, quite the contrary.  We
have several customer workloads that got negatively impacted when the
limit was bumped.

My point was that arguing about what the default should be without any
data supporting the discussion is futile.

Alan> At the ATA level we can detect both the presence of command
Alan> queueing ability, and also whether the device is spinnning rust or
Alan> not, so it may be smarter defaults could be done based upon
Alan> whether the device is an SSD or not.

Sure.

However, modern SSDs actually trend towards smaller I/O sizes. NVMe is
128K by default, I think. So a higher default wouldn't make any
difference there.

-- 
Martin K. Petersen	Oracle Linux Engineering
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help