From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id DITnrLlJcKsA for <dm-crypt@saout.de>;
 Sun,  2 Sep 2012 19:06:14 +0200 (CEST)
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com
 [74.125.82.178])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sun,  2 Sep 2012 19:06:13 +0200 (CEST)
Received: by weyu7 with SMTP id u7so3068414wey.37
 for <dm-crypt@saout.de>; Sun, 02 Sep 2012 10:06:13 -0700 (PDT)
Message-ID: <50439201.1080300@gmail.com>
Date: Sun, 02 Sep 2012 19:06:09 +0200
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <20120902163543.GA1581@fancy-poultry.org>
In-Reply-To: <20120902163543.GA1581@fancy-poultry.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [dm-crypt] Elevator / dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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