In computing, busdma, bus_dma and bus_space is a set of application programming interfaces designed to help make device drivers less dependent on platform-specific code, thereby allowing the host operating system to be more easily ported to new computer hardware.[1][2] This is accomplished by having abstractions for direct memory access (DMA) mapping across popular machine-independent computer buses like PCI, which are used on distinct architectures from IA-32 (NetBSD/i386) to DEC Alpha (NetBSD/alpha).[1] Additionally, some devices may come in multiple flavours supporting more than one bus, e.g., ISA, EISA, VESA Local Bus and PCI, still sharing the same core logic irrespective of the bus, and such device drivers would also benefit from this same abstraction.[1]: §1.2 Thus the rationale of busdma is to facilitate maximum code reuse across a wide range of platforms.[1]: §5

Circa 2006, bus and DMA abstractions made it possible for NetBSD to support 50 hardware platforms and 14 CPU architectures out of a single source tree, compared to the forking model used by Linux ports.[2]

Originally implemented as the "bus_dma" APIs by the developers of the NetBSD operating system,[1][3] busdma has been adopted by OpenBSD, FreeBSD and their derivatives; with FreeBSD incorporating it under a busdma umbrella (without an underscore). Both NetBSD and OpenBSD have additional "bus_space" APIs[4] that have been amalgamated into the version of busdma incorporated into FreeBSD. DragonFly BSD developers are also slowly converting their drivers to use busdma.

References

edit
  1. ^ a b c d e Jason R Thorpe; NASA Ames Research Center (1998). A Machine-Independent DMA Framework for NetBSD (PDF). Proceedings of the FREENIX Track: 1998 USENIX Annual Technical Conference. USENIX.
  2. ^ a b David Chisnall (2006-10-06). "NetBSD: Not Just for Toasters". InformIT. Prentice Hall Professional. Retrieved 2019-07-25.
  3. ^ Jason R Thorpe; NASA Ames Research Center (1997). "bus_dma, … — Bus and Machine Independent DMA Mapping Interface". BSD Cross Reference. NetBSD, FreeBSD, OpenBSD, DragonFly BSD.
  4. ^ Christopher G. Demetriou (1997). "bus_space, … — bus space manipulation functions". BSD Cross Reference. NetBSD, FreeBSD, OpenBSD, DragonFly BSD.
edit


📚 Artikel Terkait di Wikipedia

Matthew Dillon

802.11 drivers ALTQ Bluetooth BPF CARP ipfw NDIS netgraph PF Subsystems busdma DPorts ioctl kqueue moused OpenPAM sysctl hw.sensors systat SMBus People

Comparison of BSD operating systems

industry applicability. Projects spawned by NetBSD include NPF, Rump kernels, busdma, pkgsrc and NVMM. Derivatives: Force10 Networks FTOS– Powerful and robust

NetBSD

Related projects pkgsrc netpgp pcc tnftp tcsh Notable subsystems Veriexec busdma DTrace envsys LKM Rump kernel File systems and storage bioctl CHFS disklabel

DragonFly BSD

802.11 drivers ALTQ Bluetooth BPF CARP ipfw NDIS netgraph PF Subsystems busdma DPorts ioctl kqueue moused OpenPAM sysctl hw.sensors systat SMBus People

Vkernel

802.11 drivers ALTQ Bluetooth BPF CARP ipfw NDIS netgraph PF Subsystems busdma DPorts ioctl kqueue moused OpenPAM sysctl hw.sensors systat SMBus People

HAMMER2

802.11 drivers ALTQ Bluetooth BPF CARP ipfw NDIS netgraph PF Subsystems busdma DPorts ioctl kqueue moused OpenPAM sysctl hw.sensors systat SMBus People

HAMMER (file system)

802.11 drivers ALTQ Bluetooth BPF CARP ipfw NDIS netgraph PF Subsystems busdma DPorts ioctl kqueue moused OpenPAM sysctl hw.sensors systat SMBus People

Write Ahead Physical Block Logging

Related projects pkgsrc netpgp pcc tnftp tcsh Notable subsystems Veriexec busdma DTrace envsys LKM Rump kernel File systems and storage bioctl CHFS disklabel