Lines Matching refs:softirq

170 If a softirq shares data with user context, you have two problems.
171 Firstly, the current user context can be interrupted by a softirq, and
186 (``include/linux/interrupt.h``), which protects you from the softirq
193 from a softirq.
199 from a softirq. From a locking point of view, tasklets and timers are
227 Often a softirq might want to share data with itself or a tasklet/timer.
232 The same softirq can run on the other CPUs: you can use a per-CPU array
234 going so far as to use a softirq, you probably care about scalable
245 tasklet, different softirq or the same or another softirq: any of them
251 Hardware interrupts usually communicate with a tasklet or softirq.
252 Frequently this involves putting work in a queue, which the softirq will
258 If a hardware irq handler shares data with a softirq, you have two
259 concerns. Firstly, the softirq processing can be interrupted by a
267 the softirq cannot run while the irq handler is running: it can use
274 (``include/asm/smp.h``), which protects you from the softirq/tasklet/BH
501 from interrupt context: either a hardware interrupt or a softirq. An
890 softirq and user context. If you use a spin_lock() call
892 by the softirq while it holds the lock, and the softirq will then spin
907 spinlock, and a chain of hashed objects. Inside a softirq handler, you
915 lock it twice. Secondly, if the same softirq on another CPU is trying to
1420 Software Interrupt / softirq
1425   Strictly speaking a softirq is one of up to 32 enumerated software