A lot of discussion and debate exists in embedded software development about the relative merits of two interrupt handling architectures. The debate surrounds the "unified" and "segmented" models, which take very different approaches to how the critical sections of a real-time operating system are protected during interrupt servicing. This paper examines these two interrupt handling models, and introduces a novel hybrid that combines the best features of both. This hybrid does not require any changes to the user application and operates automatically with zero overhead.
I'd like to see a bit more detail on how the deferred kernel is implemented. Is it not done via an interrupt? If not, isn't there overhead involved in determining that it is available for processing?
They basically describe something what is called a deferrer procedure call (DPC) in Windows kernel or bottom-half/soft interrupt/tasklet in Linux kernel. Nothing new, except they introduce new terminology.
Code Time Technologies is a privately held company established with the single minded goal of designing, developing and distributing real-time kernel and middleware solutions.... Read More
Technical Paper
0
2
Download to Print
Add to bookmarks
2 comments
write a commentDr DSP Posted Jul 10, 2012
I'd like to see a bit more detail on how the deferred kernel is implemented. Is it not done via an interrupt? If not, isn't there overhead involved in determining that it is available for processing?
reply
llamer Posted May 2, 2013
They basically describe something what is called a deferrer procedure call (DPC) in Windows kernel or bottom-half/soft interrupt/tasklet in Linux kernel. Nothing new, except they introduce new terminology.
reply