By hardIRQ, if you mean hardware interrupts, they typically
preempt everything else in the system, except few cases in RT
mode.
Passion: https://sysplay.in (Playing with Systems)
--
You received this message because you are subscribed to the Google Groups "SysPlay's Inside Linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/CAAaR2_L3bQLD7YHhArRXZmDwL1bJsnOYgd83HFug9%2B-KSA2u3g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/fb166639-b492-9b05-8df7-669af0b2f127%40sarika-pugs.com.
softIRQs are neither process context nor hardware interrupt context. They have their own context.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/CAHB2L%2BdwROKj7obUVjA2sHHQkb7%3DgqKCRXxO6FNAfXrePut5Jg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/1276f173-deb1-a988-c081-cf1cc8cab165%40sarika-pugs.com.
Check the 14th slide in https://www.slideshare.net/anil_pugalia/interrupts-4638852
ksoftirqd is not ksoftirq: https://man.cx/ksoftirqd(9)
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/CAHB2L%2BfS8JqhcV0tEWZc3hQLotE3CbrhNeQbeaO5ztaCuT3BFA%40mail.gmail.com.