Vignesh,
You forgot to mention that schedule does not itself pick the next task.
The actual function called is pick_next_task which uses the leftmost
cached entry in the red black tree of able to run processes to run
next.
Nick
On 2015-01-28 12:53 PM, Vignesh Radhakrishnan wrote:
> Hey Sreejith,
>
Hi Vignesh,
Thank you.
I understood from your description that SCHED_SOFTIRQ has no relation
with scheduling directly but only deals with load balancing between
groups.
I have one more question regarding timer interrupts and its relation
to schedule() function. As I said, my understanding was tha
Hey Sreejith,
softirq's are run as bottom half processing (after an interrupt is handled
or when there is no work to be done -
https://www.kernel.org/doc/htmldocs/kernel-hacking/basics-softirqs.html )
and sched_softirq is one such soft irq whose only function is confined to
the routine run_rebala
Hi,
I was reading LKD by Robert Love. I got the following idea from the book.
Correct me if I am worng
I was checking through source code and I found that on every timer
interrupt, through sched/fair.c we are raising the SCHED_SOFTIRQ().
I was checking the relation between SCHED_SOFTIRQ and actu
