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 for Android: free password hash cracker in your pocket

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

Message-ID: <CANejiEURP-tuBtCfocNjrs1MgK8NMzQttRkPEWeXJ40fNov20Q@mail.gmail.com>
Date:	Tue, 11 Oct 2011 09:49:47 +0800
From:	Shaohua Li <shli@...nel.org>
To:	Ming Lei <tom.leiming@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"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?

2011/10/11 Ming Lei <tom.leiming@...il.com>:
> Hi,
>
> On Tue, Oct 11, 2011 at 12:25 AM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>> On Mon, 10 Oct 2011 22:31:34 +0800
>> Ming Lei <tom.leiming@...il.com> 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.
>>>
>>> >From comments of pm_qos_add_request usages in drivers, it can be understood
>>> as interrupt latency too, IMO.
>>>
>>> So, could we think that PM_QOS_CPU_DMA_LATENCY is interrupt latency?
>>
>> 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?
As Alan explained, PM_QOS_CPU_DMA_LATENCY is for dma snooping. For example,
in x86, cpu snoop dma. when cpu is in idle state, cpu need snoop
device dma activity, there
is latency involved for idle state.
--
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/