From: Jeff Garzik <jgarzik@pobox.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Chris Leech <christopher.leech@intel.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
Deepak Saxena <dsaxena@plexity.net>
Subject: Re: [RFC][PATCH 000 of 3] MD Acceleration and the ADMA interface: Introduction
Date: Fri, 03 Feb 2006 13:58:00 -0500 [thread overview]
Message-ID: <43E3A7B8.2050607@pobox.com> (raw)
In-Reply-To: <43E39F2B.5080408@drzeus.cx>
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
next prev parent reply other threads:[~2006-02-03 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 1:46 [RFC][PATCH 000 of 3] MD Acceleration and the ADMA interface: Introduction Dan Williams
2006-02-03 2:01 ` Jeff Garzik
2006-02-03 18:21 ` Pierre Ossman
2006-02-03 18:25 ` Randy.Dunlap
2006-02-03 18:58 ` Jeff Garzik [this message]
2006-02-06 3:30 ` Neil Brown
2006-02-06 19:25 ` Dan Williams
2006-02-07 7:23 ` Evgeniy Polyakov
2006-02-14 3:29 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 1:12 Dan Williams
2006-02-03 1:25 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E3A7B8.2050607@pobox.com \
--to=jgarzik@pobox.com \
--cc=andrew.grover@intel.com \
--cc=christopher.leech@intel.com \
--cc=dan.j.williams@intel.com \
--cc=drzeus-list@drzeus.cx \
--cc=dsaxena@plexity.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.