mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: rd bairva <rbairva@gmail.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Dmaengine query
Date: Wed, 14 Apr 2010 17:30:39 -0700	[thread overview]
Message-ID: <v2he9c3a7c21004141730vcc79dd58t5478c9d83af9816@mail.gmail.com> (raw)
In-Reply-To: <v2mdbb048f61004132326r8ac75382k1e42321ff0ed484a@mail.gmail.com>

On Tue, Apr 13, 2010 at 11:26 PM, rd bairva <rbairva@gmail.com> wrote:
> Hi Dan,
>
>        I am currently writing dmaengine compatible DMA driver for our ARM
> based architecture, But I am facing some performance issues doing
> that.
>
> 1. dmaengine says callback should run in tasklet, and next transfer
> cannot be scheduled from the callback.
>
> Due to these restrictions I am getting some performance issue while
> playing sound in our architecture.
>
>
> Can callback call in DMA driver be placed out of spin_lock to submit
> new operations from callback? (only in asynchronous case)
>
> is this Ok? please comment.

Other dma driver authors are dropping the lock across the call to the
callback in the mem-to-io case.  The compliance points in the
documentation are primarily targeted at the expectations of the
async_tx api.  In the mem-to-io (slave dma) model you are not using
the async_tx api.

--
Dan

  reply	other threads:[~2010-04-15  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  6:26 rd bairva
2010-04-15  0:30 ` Dan Williams [this message]
2010-04-19 10:26   ` rd bairva
2010-04-22  4:05     ` rd bairva
2010-05-21  8:44     ` rd bairva
2010-05-24  0:01     ` Linus Walleij

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=v2he9c3a7c21004141730vcc79dd58t5478c9d83af9816@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbairva@gmail.com \
    /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

all inboxes | Powered by JetHome®