RFC: Detect SSDs and turn on `no_{read,write}_workqueue` by default
New feature description
On SSDs, disabling the read and write workqueues significantly increases throughput and latency (possibly over 2x, source).
Would you be open to cryptsetup itself detecting whether a backing block device is on an SSD or not, and turning on the no_{read,write}_workqueue
performance tuning flags by default? Is there some hidden down side?
Additional info
carbonOS, Cryptsetup 2.7.0-rc1