Kernel scheduling as applied to office discussion

It should be considered very bad form to disable interrupts during a discussion of less than critical importance to office function. Disabling interrupts leads to discussion starvation that may delay an action beyond its usefulness. Preemptive discussion scheduling is a must to enable effective communication and smooth work flow.

An interrupting co-worker should get in the wait queue and be patient until the target can process the interrupt and give the interrupting process a time slice. The interrupt handler should do minimal and concise talking and defer further discussion to a bottom half handler. The interruptor should recognize that the target is implementing a prioritized scheduler and will defer bottom half handling depending on its relevance.

The target may then return to the original discussion and the interruptor should continue in the wait queue until such time as it is again scheduled for processing.

Hogging the scheduler and constantly running your mouth to avoid preemption is terribly rude and makes people not like you. Avoid that behavior and be a good member of society.