Messages in this thread | | | Subject | Re: __do_softirq and real-time execution context | From | Peter Zijlstra <> | Date | Mon, 04 Aug 2008 09:41:23 +0200 |
| |
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.
| |