From: Diego Calleja <diegocg@gmail.com>
To: Juan PC <piernas@ditec.um.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CFQ I/O scheduler better than AS?
Date: Wed, 22 Sep 2010 14:10:16 +0200 [thread overview]
Message-ID: <201009221410.17056.diegocg@gmail.com> (raw)
In-Reply-To: <1285152908.10774.306.camel@albahaca.inf.um.es>
On Miércoles, 22 de Septiembre de 2010 12:55:08 Juan PC escribió:
> Hi:
>
> I am sure that, for most people, the clear answer is "yes" (after all,
> CFQ is the default I/O scheduler in Linux), but we are having serious
> difficulties to find a benchmark which shows that CFQ is undoubtedly
> better than AS.
The AS io scheduler was removed in 2.6.33 (7 months ago, in commit
492af6350a5ccf087e4964104a276ed358811458), so you must be running
benchmarks in old kernels. The CFQ scheduler used in recent kernels
should have good performance (if it doesn't, you probably should
write a bug report ccing jens.axboe@oracle.com)
Saludos ;)
next prev parent reply other threads:[~2010-09-22 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 10:55 CFQ I/O scheduler better than AS? Juan PC
2010-09-22 12:10 ` Diego Calleja [this message]
2010-09-22 15:26 ` Juan PC
2010-09-23 1:22 ` Yuehai Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201009221410.17056.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piernas@ditec.um.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox