File tree Expand file tree Collapse file tree 1 file changed +3
-13
lines changed
Documentation/driver-api/pci Expand file tree Collapse file tree 1 file changed +3
-13
lines changed Original file line number Diff line number Diff line change @@ -83,19 +83,9 @@ this to include other types of resources like doorbells.
83
83
Client Drivers
84
84
--------------
85
85
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.
99
89
100
90
101
91
Orchestrator Drivers
You can’t perform that action at this time.
0 commit comments