# Noop now named none

**URL:** <https://forums.suse.com/t/noop-now-named-none/34596>\
**Category:** SUSE News\
**Created:** [November 29, 2019, 5:25pm UTC](https://forums.suse.com/t/noop-now-named-none/34596 "2019-11-29T17:25:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![InTheNews](https://avatars.discourse-cdn.com/v4/letter/i/65b543/32.png) [@InTheNews](https://forums.suse.com/u/InTheNews)\
**Post date:** [November 29, 2019, 5:25pm UTC](https://forums.suse.com/t/noop-now-named-none/34596/1 "2019-11-29T17:25:37Z")

</div>

Noop now named none

Lately more and more people approached me with saptune warnings regarding ‘noop’ being an invalid scheduler. With new Servie Packs we see a transition from non-multiqueue schedulers (noop, cfq, deadline) to multiqueue schedulers (none, mq-deadline, bfq, kyber). This transition will be finished with kernel 5.x (SLES 15 SP2). Only multiqueue schedulers will remain. Even if […]  
The post [Noop now named none](https://www.suse.com/c/noop-now-named-none/) appeared first on [SUSE Communities](https://www.suse.com/c).

[More…](https://www.suse.com/c/noop-now-named-none/)