ADMA: Difference between revisions

370 bytes removed ,  7 years ago
no edit summary
[unchecked revision][unchecked revision]
No edit summary
 
No edit summary
 
(4 intermediate revisions by 4 users not shown)
Line 1:
ADMA is a feature of some PCI diskATA controllers, thatADMA eliminates the need for the driver to send the READ and WRITE commands to the drive. The Bus Mastering Controller sets up <b>both</b> sides of every DMA transfer, and initiates the transfer itself. All the driver needs to do is set up a table of "commands" (a CPB), set some pointers, and then turn on ADMA mode. This wouldgreatly allowreduces the CPU to avoid doing anyexcessive IO port commandsoperations, and would freefrees up tremendous amounts ofprecious CPU time, if you can find a disk controller that supports it.
Multiword DMA and UDMA modes require a driver to create a PRDT to handle the controller half of DMA transfers, and additionally send READ DMA and WRITE DMA commands to the ATA device for each PRD entry in the table, through the controller. This is really quite stupid, unless there is some problem with the controller initiating the READ/WRITE commands to the drive, itself.
 
An ADMA capable controller maps the standard ATA IO and ADMA registers at a 64-bit or 32-bit address (...PCI BAR 4/5, 20h-27h). The size of this area is 1024 bytes.
ADMA is a feature of some PCI disk controllers, that eliminates the need for the driver to send the READ and WRITE commands to the drive. The Bus Mastering Controller sets up <b>both</b> sides of every DMA transfer, and initiates the transfer itself. All the driver needs to do is set up a table of "commands" (a CPB), set some pointers, and then turn on ADMA mode. This would allow the CPU to avoid doing any IO port commands, and would free up tremendous amounts of CPU time, if you can find a disk controller that supports it.
 
ADMA is supposedly built to unleash the inherent power ofsupports Queued and Overlapped ATA command sets, but neither is necessary to runsupport ADMA,. andBoth ADMA can handle boththe ATA and ATAPI commands sets are supported.
An ADMA capable controller maps all the standard ATA IO ports into 1K of memory at some 64-bit address (less than 256 bytes is currently used), including all the registers needed to control the ADMA function.
 
==Detection and Initialization==
ADMA is supposedly built to unleash the inherent power of Queued and Overlapped ATA command sets, but neither is necessary to run ADMA, and ADMA can handle both ATA and ATAPI commands.
 
The ATA/ATAPI Host Adapters Standard specifies a PCI Class Code, details initialization, and operation of ADMA devices.
Since ADMA relies on 64 bit memory addresses, it seems reasonable to assume that it will only be available on disk controllers built into motherboards built for 64 bit CPUs.
 
Note: The CPB list contains things called PRDs, but they are not formatted the same as PRDT PRDs (like the ones that are used in ATA DMA).
 
==Detection and Initialization==
 
7.4.1.6 PCI Class Code / Table 14 – ADMA PCI Class Code
An ADMA capable disk controller must have a very specific set of codes in its PCI Configuration Space.
* Programming Interface Code: 20h – Single Stepping / 30h – Continuous Operation
DevID=1841h
* Sub-class Code: 05h – ATA
RevID= 40h
* Base-Class Code: 01h – Mass Storage
ClassCode =010520h (Non-Chained Controller)
010530h (Chained Controller)
 
Several vendors have chosen ADMA mode as the basis for their SATA controller implementations, however, often these implementations contain proprietary extensions. For this reason, the PCI Class may be different... driver "quirks" may be required to support these devices.
BAR4 | BAR5 (64 bits!), contains the base address for the 64 bit memory mapped ADMA registers.
 
==See Also==
===Articles===
* [[ATA/ATAPI using DMA]]
===External Links===
* http://www.t13.org/Documents/UploadedDocuments/technical/e00149r0.pdf -- Initial specification
* http://www.t13.org/Documents/UploadedDocuments/project/d1510r1-Host-Adapter.pdf -- Latest draft of "ATA/ATAPI Host Adapters Standard"
 
{{stub}}
Anonymous user