| 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: <20090714.090055.56906831.davem@davemloft.net> Date: Tue, 14 Jul 2009 09:00:55 -0700 (PDT) From: David Miller <davem@...emloft.net> To: tglx@...utronix.de Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, kaber@...sh.net, peterz@...radead.org Subject: Re: [patch 1/3] net: serialize hrtimer callback in sched_cbq From: Thomas Gleixner <tglx@...utronix.de> Date: Tue, 14 Jul 2009 10:55:14 +0200 (CEST) > David, > > On Sun, 12 Jul 2009, David Miller wrote: > >> What should probably happen is that the hrtimer merely fires off work >> at software interrupt context (perhaps a tasklet or similar), and that >> software interrupt code take the qdisc's root lock throughout it's >> execution. > > Sigh, I almost expected that the removal of the callback modes will > fire back some day. Well this makes hrtimers decidedly less useful for networking and we have a ton of bugs right now, basically in every hrtimer used by the networking currently. The only way we can use them, as things currently stand, is as triggers for softirq work. Is it really that troublesome to provide this kind of facility generically, rather than having various subsystems replicate such code where they want to use hrtimers and are restricted to softirqs? -- 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