Home ›

Kernel Korner - I/O Schedulers

Issue 118

From Issue #118
February 2004

Feb 01, 2004  By Robert Love
 in
Here's how I/O schedulers contribute to disk performance in Linux and the improvements you can get from the new I/O schedulers in the 2.6 kernel.
Acknowledgement

Andrea Arcangeli and Jens Axboe are the primary authors of the Linus Elevator. Jens Axboe is the primary author of the Deadline I/O Scheduler. Nick Piggin is the primary author of the Anticipatory I/O Scheduler.

Robert Love (rml@tech9.net) is a kernel hacker at MontaVista Software and a student at the University of Florida. He is the author of Linux Kernel Development. Robert loves O.A.R. and lives in Gainesville, Florida.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Very informative read.

Binary Soldier's picture
Submitted by Binary Soldier (not verified) on Thu, 08/27/2009 - 19:10.

Thanks for taking the time to publish this article.

I'm currently studying operating system fundamentals at university and it was great to read on it's usage in the Linux operating system. I had learned how Linux treats all hardware items as 'files', but reading this has given me a much more in-depth understanding.

*Bookmarked*

great article

procfs's picture
Submitted by procfs (not verified) on Thu, 02/05/2009 - 05:40.

Hi this is grate, is there any other documents like this plain and symple

Thanks

Best regards

Nice article

Michael R. Hines's picture
Submitted by Michael R. Hines (not verified) on Sat, 05/05/2007 - 22:42.

I like this. It describes the problem to the point and nothing else. Thanks for writing it.

Re: Kernel Korner: I/O Schedulers

Anonymous's picture
Submitted by Anonymous on Sat, 02/14/2004 - 03:00.

Elementary my dear Watson.

That's only a mere 122 fold increase in test two.

Now for your next trick.......

Mick.

What about driver improvements?

Tom Callahan's picture
Submitted by Tom Callahan (not verified) on Wed, 04/13/2005 - 16:40.

Your discounting the fact that there are many other performance enhancing improvements to the 2.6 kernel that have highly boosted read/write performance. Especially in the form of better supported IDE/SCSI devices and better drivers and feature sets.

I agree that anticipatory scheduler is MUCH better than the older schedulers, but recognize hardware/software improvements as well.

Anticipatory is not the best for everyone also, I recommend any person or company to run many many tests that will emulate your environment to test which scheduler is best for you...

-Tom

Nice article. However, I

Anonymous's picture
Submitted by Anonymous (not verified) on Mon, 01/18/2010 - 14:51.

Nice article. However, I agree that schedulers needs to be tested in a particular environment to be sure which choice is best.

For example, AS is a poor choice for RAID and/or virtual machines. Virtual hosts with RAID disks appear to work best with the deadline elevator. VM guests should use the noop elevator so not to disguise physical access with virtual characteristics, let alone the ineffective and unnecessary overhead of using AS in a VM guest.

-shubes

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions