diff options
| author | Eric Farman <farman@linux.ibm.com> | 2022-08-04 23:39:26 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2022-08-04 16:19:15 -0600 |
| commit | bc792884b76f0da2f5c9a8d720e430e2de9756f5 (patch) | |
| tree | 667c8e0309f378062702eedf204820889bed0382 /include/crypto | |
| parent | bcee43dc6d5bd6f54e5e2a5d696bf8c8f4c141dd (diff) | |
| download | linux-bc792884b76f0da2f5c9a8d720e430e2de9756f5.tar.bz2 | |
s390/dasd: Establish DMA alignment
linux-next commit bf8d08532bc1 ("iomap: add support for dma aligned
direct-io") changes the alignment requirement to come from the block
device rather than the block size, and the default alignment
requirement is 512-byte boundaries. Since DASD I/O has page
alignments for IDAW/TIDAW requests, let's override this value to
restore the expected behavior.
Make this change for both ECKD and DIAG disciplines, as they both
would fall into this category. Leave FBA alone, since it is always
comprised of 512-byte blocks.
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Acked-by: Halil Pasic <pasic@linux.ibm.com>
Reviewed-by: Stefan Haberland <sth@linux.ibm.com>
Signed-off-by: Stefan Haberland <sth@linux.ibm.com>
Link: https://lore.kernel.org/r/20220804213926.3361574-3-sth@linux.ibm.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include/crypto')
0 files changed, 0 insertions, 0 deletions