Skip to content

Commit 9a000a7

Browse files
tstrukbjorn-helgaas
authored andcommitted
PCI/P2PDMA: Remove reference to pci_p2pdma_map_sg()
Update Documentation/driver-api/pci/p2pdma.rst doc and remove references to obsolete p2pdma mapping functions. Fixes: 0d06132 ("PCI/P2PDMA: Remove pci_p2pdma_[un]map_sg()") Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Bjorn Helgaas <[email protected]> Reviewed-by: Logan Gunthorpe <[email protected]> Cc: [email protected]
1 parent b85ea95 commit 9a000a7

File tree

1 file changed

+3
-13
lines changed

1 file changed

+3
-13
lines changed

Documentation/driver-api/pci/p2pdma.rst

Lines changed: 3 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -83,19 +83,9 @@ this to include other types of resources like doorbells.
8383
Client Drivers
8484
--------------
8585

86-
A client driver typically only has to conditionally change its DMA map
87-
routine to use the mapping function :c:func:`pci_p2pdma_map_sg()` instead
88-
of the usual :c:func:`dma_map_sg()` function. Memory mapped in this
89-
way does not need to be unmapped.
90-
91-
The client may also, optionally, make use of
92-
:c:func:`is_pci_p2pdma_page()` to determine when to use the P2P mapping
93-
functions and when to use the regular mapping functions. In some
94-
situations, it may be more appropriate to use a flag to indicate a
95-
given request is P2P memory and map appropriately. It is important to
96-
ensure that struct pages that back P2P memory stay out of code that
97-
does not have support for them as other code may treat the pages as
98-
regular memory which may not be appropriate.
86+
A client driver only has to use the mapping API :c:func:`dma_map_sg()`
87+
and :c:func:`dma_unmap_sg()` functions as usual, and the implementation
88+
will do the right thing for the P2P capable memory.
9989

10090

10191
Orchestrator Drivers

0 commit comments

Comments
 (0)