From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: device queue scheduler
Date: Thu, 18 Mar 2010 12:49:17 -0400 [thread overview]
Message-ID: <4BA2598D.8040503@cfl.rr.com> (raw)
I'm wondering why the dm block devices have a request queue at all, and
more importantly why they use the default cfq scheduler. It seems to me
that the physical disk should take care of the scheduling, and not have
that work duplicated at each layer of dm stacked on top. It wonder
though, where should the scheduler policy be set? In libdevmapper, or
by a system udev rule?
reply other threads:[~2010-03-18 16:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BA2598D.8040503@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dm-devel@redhat.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.