| 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: <BAY121-W10FA0ADF0B41AF147B9FE2B6820@phx.gbl> Date: Tue, 29 Jul 2008 06:12:04 +0000 From: Kostya B <bkostya@...mail.com> To: <netdev@...r.kernel.org> Subject: __do_softirq execution context Hello netdev, Please put your thoughts on the following: __do_softirq could be executed from interrupt, ksoftirqd or event userspace process context. There is a mechanism of limiting userspace employment in that task and waking up the ksoftirqd. In the case of real-time userspace process, such behavior may yield severe outcomes. May be it will better not to employ such process at all. Just check has_rt_policy() and immediately wakeup ksoftirqd? By now, how network driver poll() could differentiate in which context it runs? Both cases (ksoftirqd and userspace) answer positively on in_interrupt()? Regards, - Kostya _________________________________________________________________ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists