Alexander Motin 1f4a469d36 Cleanup address range checks in ioat(4). ... - Deduce allowed address range for bus_dma(9) from the hardware version. Different versions (CPU generations) have different documented limits. - Remove difference between address ranges for src/dst and crc. At least docs for few recent generations of CPUs do not mention anything like that, while older are already limited with above limits. - Remove address assertions from arguments. While I do not think the addresses out of allowed ranges should realistically happen there due to the platforms physical address limitations, there is now bus_dma(9) to make sure of that, preferably via IOMMU. - Since crc now has the same address range as src/dst, remove crc_dmamap, reusing dst2_dmamap instead. Discussed with: cem MFC after: 2 weeks Sponsored by: iXsystems, Inc.		2019-11-15 22:47:59 +00:00
..
ioat.c	Cleanup address range checks in ioat(4).	2019-11-15 22:47:59 +00:00
ioat.h	ioat(4): Set __result_use_check on ioat_acquire_reserve	2019-01-17 23:21:02 +00:00
ioat_hw.h
ioat_internal.h	Cleanup address range checks in ioat(4).	2019-11-15 22:47:59 +00:00
ioat_test.c	ioatcontrol(8) could exercise 8k-aligned copy with page-break, crc and	2019-04-02 19:06:25 +00:00
ioat_test.h	ioatcontrol(8) could exercise 8k-aligned copy with page-break, crc and	2019-04-02 19:06:25 +00:00