pci_p2pdma_map_type(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to pci_p2pdma_map_type(9) from the Kernel API Manual β€” it's giving PCI peer-to-peer DMA mapping realness and I'm obsessed πŸ’…βœ¨

🌸 NAME 🌸

pci_p2pdma_map_type β€” determine the mapping type for P2PDMA transfers. That's the whole name section, periodt. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

the signature, verbatim, no cap:

enum pci_p2pdma_map_type pci_p2pdma_map_type (struct p2pdma_provider
       *provider , struct device *dev );

πŸŽ€ ARGUMENTS πŸŽ€

okay two args, both iconic:

  • provider β€” P2PDMA provider structure. no cap, that's the provider vibe.
  • dev β€” target device for the transfer. where the transfer is headed, bestie.

πŸ’œ DESCRIPTION πŸ’œ

So this function determines how peer-to-peer DMA transfers should be mapped between the provider and the target dev. The mapping type indicates whether the transfer can be done directly through PCI switches or must go through the host bridge. That's the highkey whole point: are we going direct through the switches, or are we going through the host bridge? 🫢

🌈 SEE ALSO 🌈

peep these, bestie β€” the kernel file and all the related functions:


okay that's the page, bestie πŸ’– source/version: ./drivers/pci Β· date: October 2026 Β· page: pci_p2pdma_map_type(9) β€” signing off, slay πŸ¦‹βœ¨

πŸ“¦ where this page comes from