Where IOSCHED ?

Where IOSCHED ?

[Pavel Vasilyev]

# dmesg | grep sched
[    0.387902] io scheduler noop registered
[    0.387989] io scheduler deadline registered
[    0.388079] io scheduler cfq registered (default)

# cat /boot/config-3.18.17-rt14 | grep IOSCHED
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CFQ_GROUP_IOSCHED=y
CONFIG_DEFAULT_IOSCHED="cfq"

# cat /sys/block/sda/queue/scheduler
none

# uname -a
Linux localhost 3.18.17-rt14 #1 SMP PREEMPT RT Wed Jul 22 18:49:51 MSK 2015 
x86_64 GNU/Linux
-- 

                                                          Pavel.

Re: Where IOSCHED ?

[Sebastian Andrzej Siewior]

* Pavel Vasilyev | 2015-07-22 23:05:24 [+0300]:

>[    0.388079] io scheduler cfq registered (default)
># cat /sys/block/sda/queue/scheduler
>none

Does the same thing happen with plain v3.18.17? Because if it does then
it is not a -RT problem.

># uname -a
>Linux localhost 3.18.17-rt14 #1 SMP PREEMPT RT Wed Jul 22 18:49:51
>MSK 2015 x86_64 GNU/Linux

Sebastian

Re: Where IOSCHED ?

[pavel]

23.07.2015 15:39, Sebastian Andrzej Siewior пишет:
> * Pavel Vasilyev | 2015-07-22 23:05:24 [+0300]:
>
>> [    0.388079] io scheduler cfq registered (default)
>> # cat /sys/block/sda/queue/scheduler
>> none
> Does the same thing happen with plain v3.18.17? Because if it does then
> it is not a -RT problem.
This production server, but i try compile plain kernel :)
>
>> # uname -a
>> Linux localhost 3.18.17-rt14 #1 SMP PREEMPT RT Wed Jul 22 18:49:51
>> MSK 2015 x86_64 GNU/Linux
> Sebastian

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Where IOSCHED ?

[pavel]

23.07.2015 15:39, Sebastian Andrzej Siewior пишет:
> * Pavel Vasilyev | 2015-07-22 23:05:24 [+0300]:
>> [    0.388079] io scheduler cfq registered (default)
>> # cat /sys/block/sda/queue/scheduler
>> none
> Does the same thing happen with plain v3.18.17? Because if it does then
> it is not a -RT problem.
# gzip -cd ../patch-3.18.17-rt14.patch.gz | patch -p1 -R;
#  make oldconfig; make; make install; make modules_install; reboot;
...
# cat /sys/block/{sd,md}*/queue/scheduler
none
none
none
none
none
none

Ooops  o.0

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Where IOSCHED ?

[Wolfgang M. Reimer]

On 22.07.2015 22:05, Pavel Vasilyev wrote:

> # dmesg | grep sched
> [    0.387902] io scheduler noop registered
> [    0.387989] io scheduler deadline registered
> [    0.388079] io scheduler cfq registered (default)
> 

# dmesg | grep sched
[    0.516085] io scheduler noop registered
[    0.516089] io scheduler deadline registered (default)
[    0.516096] io scheduler cfq registered

> # cat /boot/config-3.18.17-rt14 | grep IOSCHED
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_IOSCHED_CFQ=y
> CONFIG_CFQ_GROUP_IOSCHED=y
> CONFIG_DEFAULT_IOSCHED="cfq"
> 

# cat /boot/config-3.18.17-rt14 | grep IOSCHED
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CFQ_GROUP_IOSCHED=y
CONFIG_DEFAULT_IOSCHED="deadline"


> # cat /sys/block/sda/queue/scheduler
> none
> 

# cat /sys/block/sda/queue/scheduler
noop [deadline] cfq 

> # uname -a
> Linux localhost 3.18.17-rt14 #1 SMP PREEMPT RT Wed Jul 22 18:49:51 MSK 2015 x86_64 GNU/Linux

# uname -a
Linux t520-wolf 3.18.17-rt14 #1 SMP PREEMPT RT Tue Jul 7 14:23:12 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux


Hi Pavel,

so in my case /sys/block/sda/queue/scheduler shows the correct I/O
schedulers for the *same* kernel (3.18.17-rt14). The only difference is
that my default I/O scheduler is "deadline".

Wolfgang

Re: Where IOSCHED ?

[pavel]

24.07.2015 12:35, Wolfgang M. Reimer пишет:
> On 22.07.2015 22:05, Pavel Vasilyev wrote:
>
>> # dmesg | grep sched
>> [    0.387902] io scheduler noop registered
>> [    0.387989] io scheduler deadline registered
>> [    0.388079] io scheduler cfq registered (default)
>>
> # dmesg | grep sched
> [    0.516085] io scheduler noop registered
> [    0.516089] io scheduler deadline registered (default)
> [    0.516096] io scheduler cfq registered
>
>> # cat /boot/config-3.18.17-rt14 | grep IOSCHED
>> CONFIG_IOSCHED_NOOP=y
>> CONFIG_IOSCHED_DEADLINE=y
>> CONFIG_IOSCHED_CFQ=y
>> CONFIG_CFQ_GROUP_IOSCHED=y
>> CONFIG_DEFAULT_IOSCHED="cfq"
>>
> # cat /boot/config-3.18.17-rt14 | grep IOSCHED
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_IOSCHED_CFQ=y
> CONFIG_CFQ_GROUP_IOSCHED=y
> CONFIG_DEFAULT_IOSCHED="deadline"
>
>
>> # cat /sys/block/sda/queue/scheduler
>> none
>>
> # cat /sys/block/sda/queue/scheduler
> noop [deadline] cfq
>
>> # uname -a
>> Linux localhost 3.18.17-rt14 #1 SMP PREEMPT RT Wed Jul 22 18:49:51 MSK 2015 x86_64 GNU/Linux
> # uname -a
> Linux t520-wolf 3.18.17-rt14 #1 SMP PREEMPT RT Tue Jul 7 14:23:12 CEST 2015 x86_64 x86_64 x86_64 GNU/Linux
>
>
> Hi Pavel,
>
> so in my case /sys/block/sda/queue/scheduler shows the correct I/O
> schedulers for the *same* kernel (3.18.17-rt14). The only difference is
> that my default I/O scheduler is "deadline".
>
> Wolfgang
>

Maybe my mistake, but I use a Soft RAID1

$ cat /sys/block/{sd,md}*/queue/scheduler
none
none
none
none
none
none

--

Other server (Debian 6.0.10): non RT, but with soft RAID1 too.

$ uname -a
Linux mail 2.6.32-5-amd64 #1 SMP Wed Jun 17 16:09:06 UTC 2015 x86_64 GNU/Linux


$ cat /sys/block/{sd,md}*/queue/scheduler

noop anticipatory deadline [cfq]
noop anticipatory deadline [cfq]
none
none
none

here: sda,sdb,md0,md1,md2,md3

--

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html