linux-kernel - Re: __do_softirq and real-time execution context

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 04 Aug 2008 09:41:23 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Kostya B <bkostya@...mail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: __do_softirq and real-time execution context

On Mon, 2008-08-04 at 07:02 +0000, Kostya B wrote:
> Hello,
> 
> Please consider the following:
> 
> __do_softirq could be run from several checkpoints in kernel and even can employ userspace process context. 
> For example, under heavy network traffic such process could be blocked for a relatively large period until ksoftirqd wakes up and takes control for Rx/Tx. 
> 
> In the case of regular userspace process the ksoftirqd solves the kernel/user trade-off problem pretty well.
> However, in the case of _real-time_ process, such behavior may yield severe outcomes. Real-time (e.g. NTPL FIFO thread) might require short responses and low latency.
> 
> The proposal is that  __do_softirq should not run its pending tasks in the context of RT process.  Just check has_rt_policy() and immediately wake up ksoftirqd.

Please look at the -rt patches.

--
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/