diff options
author | Niklas Schnelle <schnelle@linux.ibm.com> | 2021-09-14 10:26:49 +0300 |
---|---|---|
committer | Vasily Gorbik <gor@linux.ibm.com> | 2021-10-26 16:21:30 +0300 |
commit | 6aefbf1cdf0018c5af53a3fa300a61fef0f046b6 (patch) | |
tree | 139ed883c6e7d3936e959e07ea7e1e47269fd4c2 /arch/s390/boot | |
parent | 74e74f9cb3dea0372bb317fd5a09c2762567f4f8 (diff) | |
download | linux-6aefbf1cdf0018c5af53a3fa300a61fef0f046b6.tar.xz |
s390/pci: add s390_iommu_aperture kernel parameter
Some applications map the same memory area for DMA multiple times while
also mapping significant amounts of memory. With our current DMA code
these applications will run out of DMA addresses after mapping half of
the available memory because the number of DMA mappings is constrained
by the number of concurrently active DMA addresses we support which in
turn is limited by the minimum of hardware constraints and high_memory.
Limiting the number of active DMA addresses to high_memory is only
a heuristic to save memory used by the iommu_bitmap and DMA page tables
however. This was added under the assumption that it rarely makes sense
to DMA map more than system memory.
To accommodate special applications which insist on double mapping, which
works on other platforms, allow specifying a factor of how many times
installed memory is available as DMA address space. Use 0 as a special
value to apply no constraints beyond what hardware dictates at the
expense of significantly more memory use.
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>
Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'arch/s390/boot')
0 files changed, 0 insertions, 0 deletions