summaryrefslogtreecommitdiff
path: root/drivers/block/null_blk
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2024-05-11 17:37:52 +0300
committerJens Axboe <axboe@kernel.dk>2024-05-14 02:51:06 +0300
commit928b607d1a0941f02899e5490201ec071d5d4ff5 (patch)
treea2364dec8613a1d96313e004f46d5d8f76be52f1 /drivers/block/null_blk
parenta7c840ba5fa78d7761b9fedc33d69cef44986d79 (diff)
downloadlinux-928b607d1a0941f02899e5490201ec071d5d4ff5.tar.xz
ublk_drv: set DMA alignment mask to 3
By default, this will be 511, as that's the block layer default. But drivers these days can support memory alignments that aren't tied to the sector sizes, instead just being limited by what the DMA engine supports. An example is NVMe, where it's generally set to a 32-bit or 64-bit boundary. As ublk itself doesn't really care, just set it low enough that we don't run into issues with NVMe where the required O_DIRECT memory alignment is now more restrictive on ublk than it is on the underlying device. This was triggered by spurious -EINVAL returns on O_DIRECT IO on a setup with ublk managing NVMe devices, which previously worked just fine on the NVMe device itself. With the alignment relaxed, the test works fine. Reviewed-by: Ming Lei <ming.lei@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block/null_blk')
0 files changed, 0 insertions, 0 deletions