linux-kernel - Re: [Question] PM-QoS: PM_QOS_CPU_DMA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111013040656.GE893@mgross-G62>
Date:	Wed, 12 Oct 2011 21:06:56 -0700
From:	mark gross <markgross@...gnar.org>
To:	Ming Lei <tom.leiming@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	mark gross <mgross@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux PM List <linux-pm@...r.kernel.org>
Subject: Re: [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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/