From: Libin Varghese <libinv@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: I/O Scheduling
Date: Sat, 28 Jan 2006 15:28:54 +0530 [thread overview]
Message-ID: <43DB405E.4020602@gmail.com> (raw)
Hi all,
Is there any work done on new I/O scheduling techniques (other
than as, cfq, noop, deadline)?
Regards,
Libin Varghese
next reply other threads:[~2006-01-28 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 9:58 Libin Varghese [this message]
2006-01-28 17:54 ` I/O Scheduling Florian Schmidt
2006-01-28 18:08 ` Lee Revell
2006-01-28 19:18 ` Jens Axboe
2006-01-28 19:44 ` Lee Revell
2006-01-28 21:28 ` 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=43DB405E.4020602@gmail.com \
--to=libinv@gmail.com \
--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