linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: Phil.Nitschke@avalon.com.au
Cc: linuxppc-embedded <Linuxppc-embedded@ozlabs.org>
Subject: Re: linux DMA capabilities in MV64460
Date: Wed, 08 Mar 2006 22:36:18 +0000	[thread overview]
Message-ID: <1141857378.28095.22.camel@localhost.localdomain> (raw)
In-Reply-To: <kwlkvomcxp.fsf@lamorak.int.avalon.com.au>

On Mon, 2006-03-06 at 14:39 +1030, Phil Nitschke wrote:
> How is a DMA controlled (from a device driver writer's perspective) when
> a third-party (i.e. in the bridge) DMA controller needs to do the work
> to get the data from a PCI Target into main memory?
> 
> What kernel API should be provided by the DMA Controller Driver?  

There is no current API for this in the kernel, but there are some
proposals. From Intel, we have I/OAT, which targets network operations:
http://lkml.org/lkml/2006/3/3/219

There's some overlap with the ADMA feature set, which is intended to
accelerate RAID operations:
http://lkml.org/lkml/2006/2/2/442


-- 
Adrian Cox <adrian@humboldt.co.uk>

  parent reply	other threads:[~2006-03-08 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <kw3bkovcup.fsf@lamorak.int.avalon.com.au>
2005-12-20  1:01 ` linux DMA capabilities in MV64460 Mark A. Greer
2005-12-20 14:27   ` Brian Waite
2005-12-20 17:54     ` Mark A. Greer
2005-12-22  0:54   ` Phil Nitschke
2006-03-06  4:09   ` Phil Nitschke
2006-03-06 13:21     ` Brian Waite
2006-03-08 14:02       ` Phil Nitschke
2006-03-08 22:36     ` Adrian Cox [this message]
2006-03-09  8:02       ` Phil Nitschke
2005-12-22  2:59 KokHow Teh

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=1141857378.28095.22.camel@localhost.localdomain \
    --to=adrian@humboldt.co.uk \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=Phil.Nitschke@avalon.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).