diff options
author | Nicolin Chen | 2020-09-01 15:16:46 -0700 |
---|---|---|
committer | Christoph Hellwig | 2020-09-03 18:14:57 +0200 |
commit | 135ba11a7a07b4ce9197d9fa4b196329a57f1e06 (patch) | |
tree | 8ffbf80dc41135d70477e4e8dfe5a5ed92b6dde2 /crypto/khazad.c | |
parent | 1e9d90dbed120ec98517428ffff4dacd9797e39d (diff) |
dma-mapping: set default segment_boundary_mask to ULONG_MAX
The default segment_boundary_mask was set to DMA_BIT_MAKS(32)
a decade ago by referencing SCSI/block subsystem, as a 32-bit
mask was good enough for most of the devices.
Now more and more drivers set dma_masks above DMA_BIT_MAKS(32)
while only a handful of them call dma_set_seg_boundary(). This
means that most drivers have a 4GB segmention boundary because
DMA API returns a 32-bit default value, though they might not
really have such a limit.
The default segment_boundary_mask should mean "no limit" since
the device doesn't explicitly set the mask. But a 32-bit mask
certainly limits those devices capable of 32+ bits addressing.
So this patch sets default segment_boundary_mask to ULONG_MAX.
Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
Acked-by: Niklas Schnelle <schnelle@linux.ibm.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'crypto/khazad.c')
0 files changed, 0 insertions, 0 deletions