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

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

Message-ID: <20100617124343.5889067c@lxorguk.ukuu.org.uk>
Date:	Thu, 17 Jun 2010 12:43:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tejun Heo <tj@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Arjan van de Ven <arjan@...radead.org>, mingo@...e.hu,
	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

On Thu, 17 Jun 2010 13:23:27 +0200
Tejun Heo <tj@...nel.org> wrote:

> On 06/17/2010 01:12 PM, Thomas Gleixner wrote:
> >> Hmmm.... oh, I see.  Wouldn't it be much better to use moving avg of
> >> IRQ durations instead of letting the driver specify it?  Drivers are
> >> most likely to just hard code it and It's never gonna be accurate.
> > 
> > Right, but that's probably more accurate than the core code heuristics
> > ever will be.
> 
> Eh, not really.  For ATA at least, there will be three different
> classes of devices.  SSDs, hard drives and optical devices

At least four: It may also be battery backed RAM.

Alan


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