Title
The case for active device drivers
Abstract
We revisit the device-driver architecture supported by the majority of operating systems, where a driver is a passive object that does not have its own thread of control and is only activated when an external thread invokes one of its entry points. This architecture complicates driver development and induces errors in two ways. First, since multiple threads can invoke the driver concurrently, it must take care to synchronise the invocations to avoid race conditions. Second, since every invocation occurs in the context of its own thread, the driver cannot rely on programming-language constructs to maintain its control flow. Both issues make the control logic of the driver difficult to implement and even harder to understand and verify. To address these issues, we propose a device-driver architecture where each driver has its own thread of control and communicates with other threads in the system via message passing. We show how this architecture addresses both of the above problems. Unlike previous message-based driver frameworks, it does not require any special language support and can be implemented inside an existing operating system as a kernel extension. We present our Linux-based implementation in progress and report on preliminary performance results.
Year
DOI
Venue
2010
10.1145/1851276.1851283
ApSys
Keywords
Field
DocType
control flow,architecture address,multiple thread,previous message-based driver framework,driver development,own thread,control logic,driver concurrently,active device driver,external thread,device-driver architecture,operating system,concurrency,message passing,programming language,race condition
Kernel (linear algebra),Architecture,Computer science,Concurrency,Control flow,Thread (computing),Control logic,Operating system,Message passing,Active devices,Embedded system
Conference
Citations 
PageRank 
References 
10
0.51
8
Authors
3
Name
Order
Citations
PageRank
Leonid Ryzhyk121216.05
Yanjin Zhu2191.68
Gernot Heiser32525137.42