lkml.org 
[lkml]   [2011]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Question] PM-QoS: PM_QOS_CPU_DMA_LATENCY == interrupt latency?
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


\
 
 \ /
  Last update: 2011-10-13 06:09    [W:0.053 / U:1.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site