The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ming Lei <tom.leiming@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	mark gross <mgross@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM List <linux-pm@vger.kernel.org>
Subject: Re: [Question] PM-QoS: PM_QOS_CPU_DMA_LATENCY == interrupt latency?
Date: Tue, 11 Oct 2011 11:07:28 +0100	[thread overview]
Message-ID: <20111011110728.13004b1c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CACVXFVNAFTpZEOnH+6LxUk=dXtNKvmYVx5NtuJJ1bri4XEyt5Q@mail.gmail.com>

> > No. Well it may be on some platforms but it isn't the same thing. On some
> > devices a DMA transfer doesn't need the CPU involved but needs the CPU to
> > respond within a set timescale (eg for coherency or bus arbitration). It
> 
> I understand only the CPU can respond after it is notified by a
> interrupt event, don't I?

The instruction stream being executed maybe, but not things like the cache

> Also could you give a example about how the CPU responds to a DMA transfer
> within a set timescale if it is required?

The kind of thing you are dealing with is

	DMA engine requests a cache line of data
	CPU wakes out of sleep, completes bus transaction
	CPU goes back to sleep
	DMA engine starts outputting data bits over SPI bus or similar

	repeat until done

so it's not instruction level stuff, merely bus traffic.

  parent reply	other threads:[~2011-10-11 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 14:31 [Question] PM-QoS: PM_QOS_CPU_DMA_LATENCY == interrupt latency? Ming Lei
2011-10-10 16:25 ` Alan Cox
2011-10-11  1:28   ` Ming Lei
2011-10-11  1:49     ` Shaohua Li
2011-10-11  2:18       ` Ming Lei
2011-10-11  2:26         ` Shaohua Li
2011-10-11  3:40           ` Ming Lei
2011-10-11  5:32             ` Shaohua Li
2011-10-11  9:36               ` Ming Lei
2011-10-11 10:07     ` Alan Cox [this message]
2011-10-11 10:56       ` Ming Lei
2011-10-13  4:06 ` mark gross
2011-10-13 14:52   ` Ming Lei

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=20111011110728.13004b1c@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=rjw@sisk.pl \
    --cc=tom.leiming@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