linux-kernel - Re: [PATCH 09/12] irq: implement IRQ expecting

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: <4C1C87DC.6060405@kernel.org>
Date:	Sat, 19 Jun 2010 11:03:24 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Arjan van de Ven <arjan@...radead.org>, mingo@...e.hu,
	tglx@...utronix.de, bphilips@...e.de, yinghai@...nel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, jeff@...zik.org,
	linux-ide@...r.kernel.org, stern@...land.harvard.edu,
	gregkh@...e.de, khali@...ux-fr.org
Subject: Re: [PATCH 09/12] irq: implement IRQ expecting

Hello,

On 06/19/2010 11:00 AM, Andi Kleen wrote:
>> IIUC, it's not to help or optimize polling itself.  It just gives us a
>> way to estimate when the next interrupt would be so that power can be
>> optimized for non polling cases.
> 
> Shouldn't the idle governour estimate this already?

I'm not an expert on the subject.  According to Arjan,

  One of the hard cases right now that the C state code has is that it
  needs to predict the future. While it has a ton of heuristics,
  including some is there IO oustanding" ones, libata is a really good
  case: libata will know generally that within one seek time (5 msec
  on rotating rust, much less on floating electrons) there'll be an
  interrupt (give or take, but this is what we can do heuristics for
  on a per irq level).  So it's a good suggestion of what the future
  will be like, MUCH better than any hint we have right now... all we
  have right now is some history, and when the next timer is....

So, it seems like it would help.

Thanks.

-- 
tejun
--
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/