From: Nate Diller <nate.diller@gmail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: io scheduler silly question perhaps..
Date: Thu, 28 Jul 2005 17:52:22 -0700 [thread overview]
Message-ID: <5c49b0ed0507281752b9485@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0507290130000.1030@skynet>
Try benchmarking Anticipatory or Deadline against Noop, preferably
with your actual workload. Noop is probably what you want, since
there is not much use in avoiding large "seeks". It could be though
that request merging, which the non-noop schedulers all perform, willl
cause Noop to lose. I haven't tried any I/O scheduler benchmarks with
flash, but perhaps we need a simple "merge only" scheduler for this
sort of thing.
Let me know what the results are.
NATE
On 7/28/05, Dave Airlie <airlied@linux.ie> wrote:
>
> I have an embedded system which has two read-only flash devices (one a
> PIO ATA flash disk, and one MDMA capable flash)
>
> As I'm doing no writing in this system and most of my reads are sequential
> (streaming movies or images) would my choice of io scheduler be very
> important?
>
> Regards,
> Dave.
>
> --
> David Airlie, Software Engineer
> http://www.skynet.ie/~airlied / airlied at skynet.ie
> Linux kernel - DRI, VAX / pam_smb / ILUG
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-07-29 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 0:31 io scheduler silly question perhaps Dave Airlie
2005-07-29 0:52 ` Nate Diller [this message]
2005-07-29 7:27 ` Jens Axboe
2005-07-29 17:56 ` Nate Diller
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=5c49b0ed0507281752b9485@mail.gmail.com \
--to=nate.diller@gmail.com \
--cc=airlied@linux.ie \
--cc=linux-kernel@vger.kernel.org \
/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