From: Jens Axboe <axboe@suse.de>
To: Vishal Patil <vishpat@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: CSCAN vs CFQ I/O scheduler benchmark results
Date: Sun, 11 Jun 2006 20:58:55 +0200 [thread overview]
Message-ID: <20060611185854.GF13556@suse.de> (raw)
In-Reply-To: <4745278c0606091915n3ed7563do505664c4f8070f81@mail.gmail.com>
On Fri, Jun 09 2006, Vishal Patil wrote:
> The machine configuation is as follows
> CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz
> Memory: 1027500 KB (1 GB)
> Filesystem: ext3
> Kernel: 2.6.16.2
You don't mention the storage used, which is quite relevant.
If you have the time, please rerun with 2.6.17-rc6-gitX latest. Although
I'm not sure why you think CSCAN is a good scheduling algorithm, in
general it may be fine but there are trivial non-root 'dos' attacks. Any
of the non-noop Linux io schedulers is a better choice imo.
--
Jens Axboe
next prev parent reply other threads:[~2006-06-11 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 19:30 CSCAN vs CFQ I/O scheduler benchmark results Vishal Patil
2006-06-10 2:15 ` Vishal Patil
2006-06-11 10:09 ` Jan Engelhardt
2006-06-11 18:58 ` Jens Axboe [this message]
2006-06-11 23:47 ` Vishal Patil
2006-06-12 6:41 ` Jens Axboe
2006-06-12 17:38 ` Vishal Patil
2006-06-12 22:21 ` Nate Diller
2006-06-13 5:46 ` Jens Axboe
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=20060611185854.GF13556@suse.de \
--to=axboe@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vishpat@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.