From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/2] Fix the mq-deadline async_depth implementation
Date: Thu, 9 May 2024 10:01:47 -0700 [thread overview]
Message-ID: <20240509170149.7639-1-bvanassche@acm.org> (raw)
Hi Jens,
The mq-deadline 'async_depth' sysfs attribute doesn't behave as intended. This
patch series fixes the implementation of that attribute.
Please consider this patch series for the next merge window.
Thanks,
Bart.
Changes compared to v1: replaced patch 1/2 with a patch from Christoph.
Bart Van Assche (2):
block: Call .limit_depth() after .hctx has been set
block/mq-deadline: Fix the tag reservation code
block/blk-mq.c | 12 ++++++------
block/mq-deadline.c | 20 +++++++++++++++++---
2 files changed, 23 insertions(+), 9 deletions(-)
next reply other threads:[~2024-05-09 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 17:01 Bart Van Assche [this message]
2024-05-09 17:01 ` [PATCH v2 1/2] block: Call .limit_depth() after .hctx has been set Bart Van Assche
2024-05-09 17:01 ` [PATCH v2 2/2] block/mq-deadline: Fix the tag reservation code Bart Van Assche
2024-05-16 8:14 ` YangYang
2024-05-16 21:27 ` Bart Van Assche
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=20240509170149.7639-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).