| 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
| ||
|
Message-ID: <4C1A05AF.5010405@kernel.org> Date: Thu, 17 Jun 2010 13:23:27 +0200 From: Tejun Heo <tj@...nel.org> To: Thomas Gleixner <tglx@...utronix.de> CC: 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 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 and if we get running avg w/ fairly large stability part, the numbers wouldn't be too far off and there's no reliable way for the driver to tell which type of device is on the other side of the cable. So, I think running avg would work much better. 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/
Powered by blists - more mailing lists