From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Elevator / dm-crypt
Date: Sun, 02 Sep 2012 19:06:09 +0200 [thread overview]
Message-ID: <50439201.1080300@gmail.com> (raw)
In-Reply-To: <20120902163543.GA1581@fancy-poultry.org>
On 09/02/2012 06:35 PM, Heinz Diehl wrote:
> assuming /dev/sda1 is an LUKS/dmcrypt encrypted partition. The default
> elevator is "noop" (given in kernel command-line), but "cfq" is set
> for /dev/sda in /sys/block/sda/queue/scheduler.
>
> What elevator is used for the underlying /dev/mapper/dm-0 (sda1)?
Partitions just use whole device elevator.
And it should be default from your kernel parameter configuration
if not set by some script later... is that param correct?
Anyway, you can just switch it later using
echo "noop">/sys/block/sda/queue/scheduler
Device-mapper devices (except request based - which is currently multipath only)
do not use own elevator at all. So only elevator for underlying device is important.
BTW you can easily check it with lsblk -t.
Or explicitly name fields - here is example of my nb with SSD
(default sched. is noop for me):
# lsblk -o NAME,TYPE,SCHED /dev/sdb
NAME TYPE SCHED
sdb disk noop
├─sdb1 part noop
├─sdb2 part noop
│ └─sdb2_crypt (dm-0) crypt
│ ├─mnbook-data (dm-1) lvm
│ ├─nbook-swap (dm-2) lvm
│ └─nbook-root64 (dm-3) lvm
└─sdb3 part noop
> sys/block/dm-0/queue/scheduler contains "none", btw.
Yes, it is irrelevant for dm-crypt, there is no elevator.
(If you ask why there is <dev>/queue dir then, the because someone
decided to put some important attributes there which applies even
when elevator is not set. No idea why...)
Milan
next prev parent reply other threads:[~2012-09-02 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 16:35 [dm-crypt] Elevator / dm-crypt Heinz Diehl
2012-09-02 17:06 ` Milan Broz [this message]
2012-09-02 17:45 ` Heinz Diehl
2012-09-02 19:17 ` Milan Broz
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=50439201.1080300@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
/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.