• Documents
  • Authors
  • Tables
  • Other Seers ▼
    RefSeer AckSeer CollabSeer SeerSeer
  • Log in
  • Sign up
  • MetaCart

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations | Disambiguate

Recovering device drivers (2004)

Cached

  • Download as a PDF

Download Links

  • [www.usenix.org]
  • [www.cs.biu.ac.il]
  • [www.cs.ualberta.ca]
  • [www.usenix.org.]
  • [www.cs.umass.edu]
  • [www.cs.princeton.edu]
  • [nooks.cs.washington.edu]
  • [www.cs.rice.edu]
  • [www.cs.wisc.edu]
  • [www.cs.washington.edu]
  • [www.cs.wisc.edu]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Michael M. Swift , Brian N. Bershad , Henry M. Levy
Venue:In OSDI
Citations:90 - 8 self
  • Summary
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@INPROCEEDINGS{Swift04recoveringdevice,
    author = {Michael M. Swift and Brian N. Bershad and Henry M. Levy},
    title = {Recovering device drivers},
    booktitle = {In OSDI},
    year = {2004},
    pages = {1--16}
}

Years of Citing Articles

Bookmark

citeulike Connotea Bibsonomy Del.icio.us Digg Reddit

OpenURL

 

Abstract

This paper presents a new mechanism that enables applications to run correctly when device drivers fail. Because device drivers are the principal failing component in most systems, reducing driver-induced failures greatly improves overall reliability. Earlier work has shown that an operating system can survive driver failures [33], but the applications that depend on them cannot. Thus, while operating system reliability was greatly improved, application reliability generally was not. To remedy this situation, we introduce a new operating system mechanism called a shadow driver. A shadow driver monitors device drivers and transparently recovers from driver failures. Moreover, it assumes the role of the failed driver during recovery. In this way, applications using the failed driver, as well as the kernel itself, continue to function as expected. We implemented shadow drivers for the Linux operating system and tested them on over a dozen device drivers. Our results show that applications and the OS can indeed survive the failure of a variety of device drivers. Moreover, shadow drivers impose minimal performance overhead. Lastly, they can be introduced with only modest changes to the OS kernel and with no changes at all to existing device drivers. 1

Citations

1236 Transaction Processing: Concepts and Techniques - Gray, Reuter - 1993
627 Efficient software-based fault isolation - Wahbe, Lucco, et al. - 1993
561 Exokernel: An operating system architecture for application-level resource management - Engler, Kaashoek, et al. - 1995
309 On µ-kernel construction - Liedtke - 1995
251 Libckpt: Transparent Checkpointing under Unix - Plank, Beck, et al. - 1995
251 A new kernel foundation for UNIX development - Mach - 1986
238 Dealing with disaster: Surviving misbehaved kernel extensions - Seltzer, Endo, et al. - 1996
199 An Empirical Study of Operating Systems Errors - Chou, Yang, et al. - 2001
192 Improving the Reliability of Commodity Operating Systems - Swift, Bershad, et al. - 2003
177 Hypervisor-based fault tolerance - Bressoud, Schneider - 1995
171 Why do computers stop and what can be done about it - Gray - 1986
124 Fault tolerance under UNIX - Borg, Blau, et al. - 1989
122 A NonStop Kernel - Bartlett - 1981
105 The Rio File Cache: Surviving Operating System Crashes - Chen, Ng, et al. - 1996
88 Recursive Restartability: Turning the Reboot Sledgehammer into a Scalpel. HotOS - Candea, Fox - 2001
68 Self-paging in the Nemesis operating system - Hand - 1999
51 Integrating segmentation and paging protection for safe, efficient and transparent software extensions - CHIUEH, VENKITACHALAM, et al. - 1999
51 The flux oskit: A substrate for os and language research - Ford, Back, et al. - 1997
46 Exploring failure transparency and the limits of generic recovery - Lowell, Chandra, et al. - 2000
40 Recovery-oriented computing (ROC): motivation, definition, techniques, and case studies - Patterson, Brown, et al. - 2002
36 How Fail-Stop are Faulty Programs - Chandra, Chen - 1998
32 Discount checking: Transparent, low-overhead recovery for general applications - Lowell, Chen - 1998
30 Whither Generic Recovery from Application Faults? A Fault Study using Open-Source - Chandra, Chen
26 Integrity S2: A fault-tolerant Unix platform - Jewett - 1991
15 Making the Case for Efficient Supercomputing - Feng
14 TFT: A software system for applicationtransparent fault tolerance - Bressoud - 1998
13 Recovery Guarantees for General Multi-Tier Applications - Barga, Lomet, et al. - 2002
10 System Support for OpenGL Direct Rendering,” Graphics Znrerface 95 - Kilgard, Blythe, et al. - 1995
10 Application transparent fault management in Fault Tolerant Mach - Russinovich, Segall, et al. - 1993
10 Lessons from FTM: An experiment in design and implementation of a low-cost fault-tolerant system - Muller, Banâtre, et al. - 1996
7 Software’s Invisible Users - Whittaker - 2001
7 Reliable hardware-software architecture - Wulf - 1975
6 Fault-tolerant computing based on Mach - Babao˘glu - 1990
4 Methods for safe and efficient implementations of virtual machines - Wahbe, Lucco - 1998
3 Fault resilient drivers for Longhorn server - Arthur - 2004
1 Vice President of Windows Core Technology, Microsoft Corp. private communication - Short - 2003
1 Systems Crash Analyst, Windows Core OS Group, Microsoft Corp. private communication - Orgovan - 2004
The National Science Foundation
  • About CiteSeerX
  • Submit Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2010 The Pennsylvania State University