From: Paolo Valente <paolo.valente@linaro.org> To: Jens Axboe <axboe@fb.com> Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org, Linux-Kernal <linux-kernel@vger.kernel.org>, Omar Sandoval <osandov@fb.com>, Linus Walleij <linus.walleij@linaro.org>, Ulf Hansson <ulf.hansson@linaro.org>, Mark Brown <broonie@kernel.org> Subject: Re: [PATCHSET v4] blk-mq-scheduling framework Date: Mon, 19 Dec 2016 12:32:37 +0100 [thread overview] Message-ID: <7A8A5078-E9B8-4EBF-BAB1-9E8EEBF3A043@linaro.org> (raw) In-Reply-To: <1481933536-12844-1-git-send-email-axboe@fb.com> > Il giorno 17 dic 2016, alle ore 01:12, Jens Axboe <axboe@fb.com> ha = scritto: >=20 > This is version 4 of this patchset, version 3 was posted here: >=20 > https://marc.info/?l=3Dlinux-block&m=3D148178513407631&w=3D2 >=20 > =46rom the discussion last time, I looked into the feasibility of = having > two sets of tags for the same request pool, to avoid having to copy > some of the request fields at dispatch and completion time. To do = that, > we'd have to replace the driver tag map(s) with our own, and augment > that with tag map(s) on the side representing the device queue depth. > Queuing IO with the scheduler would allocate from the new map, and > dispatching would acquire the "real" tag. We would need to change > drivers to do this, or add an extra indirection table to map a real > tag to the scheduler tag. We would also need a 1:1 mapping between > scheduler and hardware tag pools, or additional info to track it. > Unless someone can convince me otherwise, I think the current approach > is cleaner. >=20 > I wasn't going to post v4 so soon, but I discovered a bug that led > to drastically decreased merging. Especially on rotating storage, > this release should be fast, and on par with the merging that we > get through the legacy schedulers. >=20 I'm to modifying bfq. You mentioned other missing pieces to come. Do you already have an idea of what they are, so that I am somehow prepared to what won't work even if my changes are right? Thanks, Paolo > Changes since v3: >=20 > - Keep the blk_mq_free_request/__blk_mq_free_request() as the > interface, and have those functions call the scheduler API > instead. >=20 > - Add insertion merging from unplugging. >=20 > - Ensure that RQF_STARTED is cleared when we get a new shadow > request, or merging will fail if it is already set. >=20 > - Improve the blk_mq_sched_init_hctx_data() implementation. =46rom = Omar. >=20 > - Make the shadow alloc/free interface more usable by schedulers > that use the software queues. =46rom Omar. >=20 > - Fix a bug in the io context code. >=20 > - Put the is_shadow() helper in generic code, instead of in = mq-deadline. >=20 > - Add prep patch that unexports blk_mq_free_hctx_request(), it's not > used by anyone. >=20 > - Remove the magic '256' queue depth from mq-deadline, replace with a > module parameter, 'queue_depth', that defaults to 256. >=20 > - Various cleanups. >=20
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Valente <paolo.valente@linaro.org> To: Jens Axboe <axboe@fb.com> Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org, Linux-Kernal <linux-kernel@vger.kernel.org>, Omar Sandoval <osandov@fb.com>, Linus Walleij <linus.walleij@linaro.org>, Ulf Hansson <ulf.hansson@linaro.org>, Mark Brown <broonie@kernel.org> Subject: Re: [PATCHSET v4] blk-mq-scheduling framework Date: Mon, 19 Dec 2016 12:32:37 +0100 [thread overview] Message-ID: <7A8A5078-E9B8-4EBF-BAB1-9E8EEBF3A043@linaro.org> (raw) In-Reply-To: <1481933536-12844-1-git-send-email-axboe@fb.com> > Il giorno 17 dic 2016, alle ore 01:12, Jens Axboe <axboe@fb.com> ha scritto: > > This is version 4 of this patchset, version 3 was posted here: > > https://marc.info/?l=linux-block&m=148178513407631&w=2 > > From the discussion last time, I looked into the feasibility of having > two sets of tags for the same request pool, to avoid having to copy > some of the request fields at dispatch and completion time. To do that, > we'd have to replace the driver tag map(s) with our own, and augment > that with tag map(s) on the side representing the device queue depth. > Queuing IO with the scheduler would allocate from the new map, and > dispatching would acquire the "real" tag. We would need to change > drivers to do this, or add an extra indirection table to map a real > tag to the scheduler tag. We would also need a 1:1 mapping between > scheduler and hardware tag pools, or additional info to track it. > Unless someone can convince me otherwise, I think the current approach > is cleaner. > > I wasn't going to post v4 so soon, but I discovered a bug that led > to drastically decreased merging. Especially on rotating storage, > this release should be fast, and on par with the merging that we > get through the legacy schedulers. > I'm to modifying bfq. You mentioned other missing pieces to come. Do you already have an idea of what they are, so that I am somehow prepared to what won't work even if my changes are right? Thanks, Paolo > Changes since v3: > > - Keep the blk_mq_free_request/__blk_mq_free_request() as the > interface, and have those functions call the scheduler API > instead. > > - Add insertion merging from unplugging. > > - Ensure that RQF_STARTED is cleared when we get a new shadow > request, or merging will fail if it is already set. > > - Improve the blk_mq_sched_init_hctx_data() implementation. From Omar. > > - Make the shadow alloc/free interface more usable by schedulers > that use the software queues. From Omar. > > - Fix a bug in the io context code. > > - Put the is_shadow() helper in generic code, instead of in mq-deadline. > > - Add prep patch that unexports blk_mq_free_hctx_request(), it's not > used by anyone. > > - Remove the magic '256' queue depth from mq-deadline, replace with a > module parameter, 'queue_depth', that defaults to 256. > > - Various cleanups. >
next prev parent reply other threads:[~2016-12-19 11:32 UTC|newest] Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-17 0:12 [PATCHSET v4] blk-mq-scheduling framework Jens Axboe 2016-12-17 0:12 ` [PATCH 1/8] block: move existing elevator ops to union Jens Axboe 2016-12-17 0:12 ` [PATCH 2/8] blk-mq: make mq_ops a const pointer Jens Axboe 2016-12-17 0:12 ` [PATCH 3/8] block: move rq_ioc() to blk.h Jens Axboe 2016-12-20 10:12 ` Paolo Valente 2016-12-20 10:12 ` Paolo Valente 2016-12-20 15:46 ` Jens Axboe 2016-12-20 22:14 ` Jens Axboe 2016-12-17 0:12 ` [PATCH 4/8] blk-mq: un-export blk_mq_free_hctx_request() Jens Axboe 2016-12-17 0:12 ` [PATCH 5/8] blk-mq: export some helpers we need to the scheduling framework Jens Axboe 2016-12-17 0:12 ` [PATCH 6/8] blk-mq-sched: add framework for MQ capable IO schedulers Jens Axboe 2016-12-20 11:55 ` Paolo Valente 2016-12-20 11:55 ` Paolo Valente 2016-12-20 15:45 ` Jens Axboe 2016-12-21 2:22 ` Jens Axboe 2016-12-22 15:20 ` Paolo Valente 2016-12-22 15:20 ` Paolo Valente 2016-12-22 9:59 ` Paolo Valente 2016-12-22 9:59 ` Paolo Valente 2016-12-22 11:13 ` Paolo Valente 2016-12-22 11:13 ` Paolo Valente 2017-01-17 2:47 ` Jens Axboe 2017-01-17 2:47 ` Jens Axboe 2017-01-17 10:13 ` Paolo Valente 2017-01-17 10:13 ` Paolo Valente 2017-01-17 12:38 ` Jens Axboe 2017-01-17 12:38 ` Jens Axboe 2016-12-23 10:12 ` Paolo Valente 2016-12-23 10:12 ` Paolo Valente 2017-01-17 2:47 ` Jens Axboe 2017-01-17 9:17 ` Paolo Valente 2017-01-17 9:17 ` Paolo Valente 2016-12-17 0:12 ` [PATCH 7/8] mq-deadline: add blk-mq adaptation of the deadline IO scheduler Jens Axboe 2016-12-20 9:34 ` Paolo Valente 2016-12-20 9:34 ` Paolo Valente 2016-12-20 15:46 ` Jens Axboe 2016-12-21 11:59 ` Bart Van Assche 2016-12-21 11:59 ` Bart Van Assche 2016-12-21 14:22 ` Jens Axboe 2016-12-22 16:07 ` Paolo Valente 2016-12-22 16:07 ` Paolo Valente 2017-01-17 2:47 ` Jens Axboe 2017-01-17 2:47 ` Jens Axboe 2016-12-22 16:49 ` Paolo Valente 2016-12-22 16:49 ` Paolo Valente 2017-01-17 2:47 ` Jens Axboe 2017-01-20 11:07 ` Paolo Valente 2017-01-20 11:07 ` Paolo Valente 2017-01-20 14:26 ` Jens Axboe 2017-01-20 13:14 ` Paolo Valente 2017-01-20 13:14 ` Paolo Valente 2017-01-20 13:18 ` Paolo Valente 2017-01-20 13:18 ` Paolo Valente 2017-01-20 14:28 ` Jens Axboe 2017-01-20 14:28 ` Jens Axboe 2017-02-01 11:11 ` Paolo Valente 2017-02-01 11:11 ` Paolo Valente 2017-02-02 5:19 ` Jens Axboe 2017-02-02 9:19 ` Paolo Valente 2017-02-02 9:19 ` Paolo Valente 2017-02-02 15:30 ` Jens Axboe 2017-02-02 15:30 ` Jens Axboe 2017-02-02 21:15 ` Paolo Valente 2017-02-02 21:15 ` Paolo Valente 2017-02-02 21:32 ` Jens Axboe 2017-02-02 21:32 ` Jens Axboe 2017-02-07 17:27 ` Paolo Valente 2017-02-07 17:27 ` Paolo Valente 2017-02-01 11:56 ` Paolo Valente 2017-02-01 11:56 ` Paolo Valente 2017-02-02 5:20 ` Jens Axboe 2017-02-16 10:46 ` Paolo Valente 2017-02-16 10:46 ` Paolo Valente 2017-02-16 15:35 ` Jens Axboe 2017-02-16 15:35 ` Jens Axboe 2016-12-17 0:12 ` [PATCH 8/8] blk-mq-sched: allow setting of default " Jens Axboe 2016-12-19 11:32 ` Paolo Valente [this message] 2016-12-19 11:32 ` [PATCHSET v4] blk-mq-scheduling framework Paolo Valente 2016-12-19 15:20 ` Jens Axboe 2016-12-19 15:20 ` Jens Axboe 2016-12-19 15:33 ` Jens Axboe 2016-12-19 18:21 ` Paolo Valente 2016-12-19 18:21 ` Paolo Valente 2016-12-19 21:05 ` Jens Axboe 2016-12-19 21:05 ` Jens Axboe 2016-12-22 15:28 ` Paolo Valente 2016-12-22 15:28 ` Paolo Valente 2017-01-17 2:47 ` Jens Axboe 2017-01-17 10:43 ` Paolo Valente 2017-01-17 10:44 ` Paolo Valente 2017-01-17 10:47 ` Paolo Valente 2017-01-17 10:49 ` Paolo Valente 2017-01-17 10:49 ` Paolo Valente 2017-01-18 16:14 ` Paolo Valente 2017-01-18 16:14 ` Paolo Valente 2017-01-18 16:21 ` Jens Axboe 2017-01-18 16:21 ` Jens Axboe 2017-01-23 17:04 ` Paolo Valente 2017-01-23 17:04 ` Paolo Valente 2017-01-23 17:42 ` Jens Axboe 2017-01-23 17:42 ` Jens Axboe 2017-01-25 8:46 ` Paolo Valente 2017-01-25 8:46 ` Paolo Valente 2017-01-25 16:13 ` Jens Axboe 2017-01-25 16:13 ` Jens Axboe 2017-01-26 14:23 ` Paolo Valente 2017-01-26 14:23 ` Paolo Valente 2016-12-22 16:23 ` Bart Van Assche 2016-12-22 16:52 ` Omar Sandoval 2016-12-22 16:52 ` Omar Sandoval 2016-12-22 16:57 ` Bart Van Assche 2016-12-22 16:57 ` Bart Van Assche 2016-12-22 17:12 ` Omar Sandoval 2016-12-22 17:39 ` Bart Van Assche 2016-12-22 17:39 ` 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=7A8A5078-E9B8-4EBF-BAB1-9E8EEBF3A043@linaro.org \ --to=paolo.valente@linaro.org \ --cc=axboe@fb.com \ --cc=axboe@kernel.dk \ --cc=broonie@kernel.org \ --cc=linus.walleij@linaro.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=osandov@fb.com \ --cc=ulf.hansson@linaro.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: linkBe 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.