| 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: <E1KdNg3-0001N5-Al@be1.7eggert.dyndns.org> Date: Wed, 10 Sep 2008 13:16:02 +0200 From: Bodo Eggert <7eggert@....de> To: Mikhail Kshevetskiy <mikhail.kshevetskiy@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Ayaz Abdulla <aabdulla@...dia.com>, Jeff Garzik <jgarzik@...ox.com> Subject: Re: forcedeth: option to disable 100Hz timer (try 2) Mikhail Kshevetskiy <mikhail.kshevetskiy@...il.com> wrote: > On some hardware no TX done interrupts are generated, thus special > 100Hz timer interrupt is required to handle this situation properly. > Other device do not require that timer interrupt feature. > > Forcedeth has a DEV_NEED_TIMERIRQ flag to mark the broken devices. > Unfortunately, nobody know the actual list of broken devices, so all > device has this flag on. Other problem, this flag is not user visible, > so the kernel recompilation is required to disable timer interrupts and > test a device. Why don't you disable the interrupt after the first TX_done interrupt (no RX pending, no RX done)? Maybe you can printk "forcedeth device [x,y] does not need timer interrupts, please send this line to you@...mple.org", too. Maybe you can even disable it if no TX is to be done. OTOH, this fix is available, it's possibly the best to use it for now. -- 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