Messages in this thread | | | Date | Fri, 03 Feb 2006 13:58:00 -0500 | From | Jeff Garzik <> | Subject | Re: [RFC][PATCH 000 of 3] MD Acceleration and the ADMA interface: Introduction |
| |
Pierre Ossman wrote: > Dan Williams wrote: > >>The ADMA (Asynchronous / Application Specific DMA) interface is proposed >>as a cross platform mechanism for supporting system CPU offload engines. >>The goal is to provide a unified asynchronous interface to support >>memory copies, block xor, block pattern setting, block compare, CRC >>calculation, cryptography etc. The ADMA interface should support a PIO >>fallback mode allowing a given ADMA engine implementation to use the >>system CPU for operations without a hardware accelerated backend. In >>other words a client coded to the ADMA interface transparently receives >>hardware acceleration for its operations depending on the features of >>the underlying platform. >> > > > I'm wondering, how common is this ADMA acronym? I've been writing a MMC
In ATA land, ADMA is a hardware ATA controller interface, similar to AHCI. We even have a pdc_adma (Pacific Digital ADMA) driver in the tree, and NVIDIA uses a variant of the ADMA interface in their SATA controllers.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |