Hello,
thanks for the reply. I was going through the sources to understand
this interesting thread of discussion. I needed to clarify the following.
Why is the do_bottom_half being called from two places
1. entry.S
(I understand that it is called after return from every
syscall/slow interrupt unless there is a nested interrupt)
2. schedule() function itself.
(Is this to invoke the bottom_half_handling(), say, in
case some process calls a sleep inside the kernel?)
What (catastrophe!) might happen if the intr_count is not
artificially incremented inside the schedule() while calling
the bottom_half?
Thanks a lot for your time
gopi
>
>
> An interrupt shouldn't wander into bottom-half code. That could wreak havoc,
> and it's therefore something to check for.
>
> Instead, interrupts must set a flag for bottom-half processing to take place
> later, when it's convenient and safe. This is what the mark_bh() function is
> for.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
