All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aras Vaichas <arasv@magtech.com.au>
To: MTD-LIST <linux-mtd@lists.infradead.org>
Subject: best IO Scheduler for MTD based embedded systems
Date: Tue, 21 Aug 2007 18:03:59 +1000	[thread overview]
Message-ID: <46CA9C6F.3080604@magtech.com.au> (raw)

Hello,

What is the recommended kernel "IO Scheduler" for a system with, say, JFFS2 on 
NAND Flash that is basically running a single application for most of its life?

In our current system we've been using the NOOP (i.e. nothing) scheduler. I'm 
currently reviewing and upgrading the kernel so I was wondering if this was the 
best choice?


Aras

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

             reply	other threads:[~2007-08-21  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21  8:03 Aras Vaichas [this message]
2007-08-21 15:16 ` best IO Scheduler for MTD based embedded systems Dan Merillat

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=46CA9C6F.3080604@magtech.com.au \
    --to=arasv@magtech.com.au \
    --cc=linux-mtd@lists.infradead.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 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.