From: Damien Le Moal <damien.lemoal@wdc.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Paolo Valente <paolo.valente@linaro.org>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Subject: [PATCH v2 0/4] IO priority fixes and improvements
Date: Fri, 6 Aug 2021 14:11:36 +0900 [thread overview]
Message-ID: <20210806051140.301127-1-damien.lemoal@wdc.com> (raw)
This series fixes problems with IO priority values handling and cleans
up several macro names and code for clarity.
Changes from v1:
* Added patch 4 to unify the default priority value used in various
places.
* Fixed patch 2 as suggested by Bart: remove extra parenthesis and move
ioprio_valid() from the uapi header to the kernel header.
* In patch 2, add priority value masking.
Damien Le Moal (4):
block: bfq: fix bfq_set_next_ioprio_data()
block: fix ioprio interface
block: rename IOPRIO_BE_NR
block: fix default IO priority handling
block/bfq-iosched.c | 10 +++++-----
block/bfq-iosched.h | 4 ++--
block/bfq-wf2q.c | 6 +++---
block/ioprio.c | 9 ++++-----
drivers/nvme/host/lightnvm.c | 2 +-
fs/f2fs/sysfs.c | 2 +-
include/linux/ioprio.h | 22 ++++++++++++++++++----
include/uapi/linux/ioprio.h | 23 +++++++++++++----------
8 files changed, 47 insertions(+), 31 deletions(-)
--
2.31.1
next reply other threads:[~2021-08-06 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 5:11 Damien Le Moal [this message]
2021-08-06 5:11 ` [PATCH v2 1/4] block: bfq: fix bfq_set_next_ioprio_data() Damien Le Moal
2021-08-06 6:33 ` Hannes Reinecke
2021-08-06 5:11 ` [PATCH v2 2/4] block: fix ioprio interface Damien Le Moal
2021-08-06 6:35 ` Hannes Reinecke
2021-08-06 6:57 ` Damien Le Moal
2021-08-06 8:38 ` Hannes Reinecke
2021-08-06 5:11 ` [PATCH v2 3/4] block: rename IOPRIO_BE_NR Damien Le Moal
2021-08-06 6:37 ` Hannes Reinecke
2021-08-06 6:52 ` Damien Le Moal
2021-08-06 5:11 ` [PATCH v2 4/4] block: fix default IO priority handling Damien Le Moal
2021-08-06 6:39 ` Hannes Reinecke
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=20210806051140.301127-1-damien.lemoal@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=paolo.valente@linaro.org \
--cc=yuchao0@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).