Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5458966ybi; Wed, 12 Jun 2019 02:54:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqwYi6UKEhabfM6vzhqjwFvzdFAxcd9yKaVSSR8JUPIfJfSHYi+lrP0reU7HpcaIlv83jFfG X-Received: by 2002:a62:f20b:: with SMTP id m11mr33208433pfh.125.1560333248912; Wed, 12 Jun 2019 02:54:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560333248; cv=none; d=google.com; s=arc-20160816; b=BdqLWt7B/q6j95wGqtXNeYm5aIx4foACcWzZ9SXa3pM5yfjh2TePAM4DHfxYNLin7V ZYYu2cscmPrqjK96M4o9sxgCisVgbtYmK+DcGPKQtCUFhIV++FYDEbWWAL9OZuouEJR8 Cy2NUW4VNj7ILZ+CeksoQoLikfe32+RTUxsG09Oj6Gs3NNkO/b/3m6g/qVQoWJegvfWJ hF83z8B+DNornQfLcnnaHov8r6bEg5EIwxhB0AlH+nWzUVbPnqzachIXZgDk4r2+M/T2 CUGz5ubACUDNXwdidhC+gC1ByJHHNvsg188CDcv0ccACLs9twPUi24n6nQNX7UVk2hFX Gjog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date; bh=VsKZ5CgltgY7KoS3eeJhdtmuJWOeBROOfef/MnT8kRE=; b=nhKWRqYuotEsUKfNvZPUXzGby2F2gG3ttzrb3nfDpBtgDGTn3JKFiMrJOu6opXDsFW jtvvaFkaFJ9MHPYI1QlCH1rWWYNnGP6ccD0zz8pzLjQZDO3cCyPcwQfE8F5jdbXXtkyx ZDn34ZAtnerBi7LdxJz/c5er0sxyXZYeepzgh6+86ZKLC39SgYSnwo/BteEXuz6pJMrC vsty8x6eqhfe728lWZ9E9rKsJr2FuoZxmv+6F6q/kz2X06feYvGWSeeBbff3ZUnWwxkV L21DOzJD7zNzDiXAzIibBjXuXh9vwQj4xQ5XyNd/oK2T77u0vFd76Y5lxfkMJg7M/FwM TZig== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a69si15780716pla.178.2019.06.12.02.53.53; Wed, 12 Jun 2019 02:54:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437743AbfFLJxn (ORCPT + 99 others); Wed, 12 Jun 2019 05:53:43 -0400 Received: from smtp.nue.novell.com ([195.135.221.5]:43724 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2437415AbfFLJxn (ORCPT ); Wed, 12 Jun 2019 05:53:43 -0400 Received: from emea4-mta.ukb.novell.com ([10.120.13.87]) by smtp.nue.novell.com with ESMTP (TLS encrypted); Wed, 12 Jun 2019 11:53:41 +0200 Received: from suselix (nwb-a10-snat.microfocus.com [10.120.13.202]) by emea4-mta.ukb.novell.com with ESMTP (TLS encrypted); Wed, 12 Jun 2019 07:50:13 +0100 Date: Wed, 12 Jun 2019 08:50:09 +0200 From: Andreas Herrmann To: Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org Subject: [PATCH] block/switching-sched.txt: Update to blk-mq schedulers Message-ID: <20190612065009.GA11361@suselix> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Remove references to CFQ and legacy block layer which are gone. Update example with what's available under blk-mq. Signed-off-by: Andreas Herrmann --- Documentation/block/switching-sched.txt | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/Documentation/block/switching-sched.txt b/Documentation/block/switching-sched.txt index 3b2612e342f1..7977f6fb8b20 100644 --- a/Documentation/block/switching-sched.txt +++ b/Documentation/block/switching-sched.txt @@ -13,11 +13,9 @@ you can do so by typing: # mount none /sys -t sysfs -As of the Linux 2.6.10 kernel, it is now possible to change the -IO scheduler for a given block device on the fly (thus making it possible, -for instance, to set the CFQ scheduler for the system default, but -set a specific device to use the deadline or noop schedulers - which -can improve that device's throughput). +It is possible to change the IO scheduler for a given block device on +the fly to select one of mq-deadline, none, bfq, or kyber schedulers - +which can improve that device's throughput. To set a specific scheduler, simply do this: @@ -30,8 +28,8 @@ The list of defined schedulers can be found by simply doing a "cat /sys/block/DEV/queue/scheduler" - the list of valid names will be displayed, with the currently selected scheduler in brackets: -# cat /sys/block/hda/queue/scheduler -noop deadline [cfq] -# echo deadline > /sys/block/hda/queue/scheduler -# cat /sys/block/hda/queue/scheduler -noop [deadline] cfq +# cat /sys/block/sda/queue/scheduler +[mq-deadline] kyber bfq none +# echo none >/sys/block/sda/queue/scheduler +# cat /sys/block/sda/queue/scheduler +[none] mq-deadline kyber bfq -- 2.13.7