[dm-crypt] Elevator / dm-crypt

Milan Broz gmazyland at gmail.com
Sun Sep 2 19:06:09 CEST 2012

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...)


More information about the dm-crypt mailing list