DMA-API.txt: fix description of pci_map_sg/dma_map_sg scatterlists handling

- pci_map_sg/dma_map_sg are used with a scatter gather list that doesn't
come from the block layer (e.g. some network drivers do).

- how IOMMUs merge adjacent elements of the scatter/gather list is
independent of how the block layer determines sees elements.

Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Tejun Heo <htejun@gmail.com>
Cc: Jens Axboe <jens.axboe@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

authored by FUJITA Tomonori and committed by Linus Torvalds 1d678f36 4280e312

+3 -5
+3 -5
Documentation/DMA-API.txt
··· 316 316 pci_map_sg(struct pci_dev *hwdev, struct scatterlist *sg, 317 317 int nents, int direction) 318 318 319 - Maps a scatter gather list from the block layer. 320 - 321 319 Returns: the number of physical segments mapped (this may be shorter 322 - than <nents> passed in if the block layer determines that some 323 - elements of the scatter/gather list are physically adjacent and thus 324 - may be mapped with a single entry). 320 + than <nents> passed in if some elements of the scatter/gather list are 321 + physically or virtually adjacent and an IOMMU maps them with a single 322 + entry). 325 323 326 324 Please note that the sg cannot be mapped again if it has been mapped once. 327 325 The mapping process is allowed to destroy information in the sg.