All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Tycho Kirchner <tychokirchner@mail.de>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: ioprio_get(2) outdated
Date: Fri, 21 May 2021 13:07:50 +0200	[thread overview]
Message-ID: <e1905f65-18c8-57dc-cb2a-c8f0d3b970b3@gmail.com> (raw)
In-Reply-To: <f959ce98-f47b-bbb0-8159-b84a84bdf3eb@mail.de>

Hi Tycho,

On 5/20/21 12:30 PM, Tycho Kirchner wrote:
> Hi,
> please update ioprio_get(2) to the today more common Multi-Queue Block 
> IO Queueing Mechanism (blk-mq). In particular:
> 
>> These system calls have an effect only when used in conjunction
>> with an I/O scheduler that supports I/O priorities.  As at kernel
>> 2.6.17 the only such scheduler is the Completely Fair Queuing
>> (CFQ) I/O scheduler.
> 
> As far as I know BFQ is the only mq-iosched which supports (read-) 
> priorities. See also [1]. The kernel Documentation/block/ioprio.txt is 
> outdated as well, I guess I'll send an email there too.
> 
> Thanks and kind regards
> Tycho Kirchner

Okay, I don't know much about it, so I'll CC Michael.

Thanks,

Alex

> 
> 
> 
> [1]: https://www.kernel.org/doc/html/latest/block/bfq-iosched.html


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
Senior SW Engineer; http://www.alejandro-colomar.es/

      reply	other threads:[~2021-05-21 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 10:30 ioprio_get(2) outdated Tycho Kirchner
2021-05-21 11:07 ` Alejandro Colomar (man-pages) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1905f65-18c8-57dc-cb2a-c8f0d3b970b3@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tychokirchner@mail.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.