Benchmarking the dependability of Windows NT4, 2000 and XP

Kalakech, Ali; Kanoun, Karama; Crouzet, Yves; Arlat, Jean

doi:10.1109/dsn.2004.1311938

Cited by 38 publications

(11 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Figure 1 depicts the software architecture of a computer system. In this paper, due to the emphasis put on the analysis of the impact of the drivers, the benchmark target (BT), according to the terminology put forward by the DBench project [18], is the OS kernel. As shown on the figure, the kernel features three main interfaces with its environment.…”

Section: Context and Definition Of The Approachmentioning

confidence: 99%

Characterization of the impact of faulty drivers on the robustness of the Linux kernel

Albinet

Arlat

Fabre

2004

International Conference on Dependable Systems and Networks, 2004

Self Cite

View full text Add to dashboard Cite

Drivers are becoming the larger part of operating systems kernels. Previous studies have shown that device drivers seem to be one of the most important sources of operating systems misbehavior. Their failure can have significant impact on the kernel and cause significant damages to the system as a whole. To objectively characterize the impact of faulty drivers, we have carried out a series of fault injection experiments. To conduct these experiments we have targeted the DPI (Driver Programming Interface) that implements the way device drivers interact with the kernel. Faults are injected on the parameters of these kernel core functions. This allows for the derivation of useful results about the failure modes induced and thus characterization of the robustness of a target kernel with respect to faulty drivers. The information gathered also enables to improve these interaction facilities.

show abstract

Section: Context and Definition Of The Approachmentioning

confidence: 99%

Characterization of the impact of faulty drivers on the robustness of the Linux kernel

Albinet

Arlat

Fabre

2004

International Conference on Dependable Systems and Networks, 2004

Self Cite

View full text Add to dashboard Cite

show abstract

“…We study actual crash instances experienced by users rather than injecting artificial faults as in the case of fuzz testing [4]. This study of crash data differs from error log analysis work done by Kalakech et al [7] in that we can determine the cause of crashes and not merely time and frequency.…”

Section: Related Researchmentioning

confidence: 99%

Crash Data Collection: A Windows Case Study

Ganapathi

Patterson

2005 International Conference on Dependable Systems and Networks (DSN'05)

View full text Add to dashboard Cite

Reliability is a rapidly growing concern in contemporary Personal Computer (PC) industry, both for computer users as well as product developers. To improve dependability, systems designers and programmers must consider failure and usage data for operating systems as well as applications. In this paper, we discuss our experience with crash and usage data collection for Windows machines. We analyze results based on crashes in the UC Berkeley EECS department.

show abstract

“…This addresses some of the challenges in establishing a benchmark, such as the development of an easy portable toolset and the collection of comparable data on various systems. Previous dependability studies involving the comparison of multiple systems were all in the area of robustness testing with respect to faults induced by applications to the OS through system-call API injection [1,2]. Past studies on the impact of transient faults focused mostly on a single OS and a single hardware platform [3,4], except [5], which compared the error behavior of Linux on Pentium and PowerPC.…”

Section: Introductionmentioning

confidence: 99%

Error Behavior Comparison of Multiple Computing Systems: A Case Study Using Linux on Pentium, Solaris on SPARC, and AIX on POWER

Chen

Jacques-Silva

Kalbarczyk

et al. 2008

2008 14th IEEE Pacific Rim International Symposium on Dependable Computing

View full text Add to dashboard Cite

This paper presents an approach to conducting experimental studies for the characterization and comparison of the error behavior in different computing systems. The proposed approach is applied to characterize and compare the error behavior of three commercial systems (Linux 2.6 on Pentium 4, Solaris 10 on UltraSPARC IIIi, and AIX 5.3 on POWER 5) under hardware transient faults. The data is obtained by conducting extensive fault injection into kernel code, kernel stack, and system registers with the NFTAPE framework while running the Apache Web Server as a workload. The error behavior comparison shows that the Linux System has the highest average crash latency, the Solaris System has the highest hang rate, and the AIX System has the lowest error sensitivity and the least amount of crashes in the more severe categories.

show abstract

Benchmarking the dependability of Windows NT4, 2000 and XP

Abstract: Abstract

Cited by 38 publications

References 16 publications

Characterization of the impact of faulty drivers on the robustness of the Linux kernel

Characterization of the impact of faulty drivers on the robustness of the Linux kernel

Crash Data Collection: A Windows Case Study

Error Behavior Comparison of Multiple Computing Systems: A Case Study Using Linux on Pentium, Solaris on SPARC, and AIX on POWER

Contact Info

Product

Resources

About