From: John Garry <john.garry@huawei.com>
To: <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <ming.lei@redhat.com>,
<kashyap.desai@broadcom.com>, <chenxiang66@hisilicon.com>,
<yama@redhat.com>, <dgilbert@interlog.com>,
John Garry <john.garry@huawei.com>
Subject: [PATCH v3 0/2] blk-mq: Request queue-wide tags for shared sbitmap
Date: Thu, 13 May 2021 20:00:56 +0800 [thread overview]
Message-ID: <1620907258-30910-1-git-send-email-john.garry@huawei.com> (raw)
This is v3 of patch/series. I have spun off a new patch for tag allocation
refactoring.
Details are in commit messages.
Changes since v2:
- Spin off separate patch for tag allocation refactoring
- Combine sched shared sbitmap code into a single function
Changes since v1:
- Embed sbitmaps in request_queue struct
- Relocate IO sched functions to blk-mq-sched.c
- Fix error path code
Please retest, thanks! For some reason I could not recreate the original
issue, but I am using qemu...
John Garry (2):
blk-mq: Some tag allocation code refactoring
blk-mq: Use request queue-wide tags for tagset-wide sbitmap
block/blk-mq-sched.c | 67 ++++++++++++++++++++++++++++++++++--------
block/blk-mq-sched.h | 2 ++
block/blk-mq-tag.c | 65 +++++++++++++++++++++++-----------------
block/blk-mq-tag.h | 9 ++++--
block/blk-mq.c | 15 ++++++++--
include/linux/blkdev.h | 4 +++
6 files changed, 116 insertions(+), 46 deletions(-)
--
2.26.2
next reply other threads:[~2021-05-13 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 12:00 John Garry [this message]
2021-05-13 12:00 ` [PATCH v3 1/2] blk-mq: Some tag allocation code refactoring John Garry
2021-05-14 2:03 ` Ming Lei
2021-05-13 12:00 ` [PATCH v3 2/2] blk-mq: Use request queue-wide tags for tagset-wide sbitmap John Garry
2021-05-14 2:05 ` Ming Lei
2021-05-14 15:36 ` [PATCH v3 0/2] blk-mq: Request queue-wide tags for shared sbitmap Jens Axboe
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=1620907258-30910-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=axboe@kernel.dk \
--cc=chenxiang66@hisilicon.com \
--cc=dgilbert@interlog.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yama@redhat.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 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.