| 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: <20080902091126.232ee570@extreme> Date: Tue, 2 Sep 2008 09:11:26 -0700 From: Stephen Hemminger <shemminger@...ux-foundation.org> To: Robert Hancock <hancockr@...w.ca> Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: forcedeth: option to disable 100Hz timer On Mon, 01 Sep 2008 18:41:44 -0600 Robert Hancock <hancockr@...w.ca> wrote: > Mikhail Kshevetskiy 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. > > > > Patch add a "disable_timerirq" option to disable interrupt timer > > mentioned above. This may be extremely usefull for laptop users. > > > > Mikhail Kshevetskiy > > > > Someone (ideally NVIDIA) should really find out what hardware actually > requires this timer IRQ and only set the flag on those chipsets rather > than blindingly setting it on everything. This patch would be useful to > test whether a chipset does need it, however. Some drivers run without TX done interrupts at all. It can be done, it just requires cleaning up the ring in the start of the next transmit, and starting a longer interval timer to cleanup leftover frames at the end of a burst. -- 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