From: mark gross <markgross@thegnar.org>
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: Wed, 12 Oct 2011 21:06:56 -0700 [thread overview]
Message-ID: <20111013040656.GE893@mgross-G62> (raw)
In-Reply-To: <CACVXFVOkwX+974=eEY5UPysXN-t9Adg6=Wn0Ts4m0vT5zQaw3g@mail.gmail.com>
On Mon, Oct 10, 2011 at 10:31:34PM +0800, Ming Lei wrote:
> Hi,
>
> Looks like it is a bit difficult to understand PM_QOS_CPU_DMA_LATENCY
> from the words' meaning.
>
> After searching from google, I don't find some useful information about
> the root cause for introducing PM_QOS_CPU_DMA_LATENCY. I understand
> it is very similar to interrupt latency. Also from the comment for
> omap_pm_set_max_mpu_wakeup_lat in file[1], the description is basically same
> with interrupt latency.
its the amount of time the CPU can take to wake up and feed a DMA
engine. Its a bit more general than interrupt latency.
> From comments of pm_qos_add_request usages in drivers, it can be understood
> as interrupt latency too, IMO.
The original 2 issues that drove its predecessor implementation where
DMA'ing data to the original intel wifi device. If the CPU snoozed too
long the wifi device would get lost and network would suffer.
The other one was something to do with generating audio pops if the cpu
didn't keep some audio buffer that was getting DMA'd to something from
underflowing.
>
> So, could we think that PM_QOS_CPU_DMA_LATENCY is interrupt latency?
nope.
--mark
>
> [1], arch/arm/plat-omap/include/plat/omap-pm.h
>
> thanks,
> --
> Ming Lei
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-13 4:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 14:31 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
2011-10-11 10:56 ` Ming Lei
2011-10-13 4:06 ` mark gross [this message]
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=20111013040656.GE893@mgross-G62 \
--to=markgross@thegnar.org \
--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
all inboxes | Powered by JetHome®