From: Yu Kuai <yukuai3@huawei.com> To: <jack@suse.cz>, <axboe@kernel.dk>, <paolo.valente@linaro.org> Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <yukuai3@huawei.com>, <yi.zhang@huawei.com> Subject: [PATCH -next v2 0/6] multiple cleanup patches for bfq Date: Sat, 21 May 2022 15:35:17 +0800 [thread overview] Message-ID: <20220521073523.3118246-1-yukuai3@huawei.com> (raw) Changes in v2: - add missing blank line in patch 1. - remove patch 7,8, since they are wrong. - add reviewed-by tag There are no functional changes in this patchset, just some places that I think can be improved during code review. This patchset is rebased based on this patchset: https://lore.kernel.org/all/20220428120837.3737765-1-yukuai3@huawei.com/ Previous version: v1: https://lore.kernel.org/all/20220514090522.1669270-1-yukuai3@huawei.com/ Yu Kuai (6): block, bfq: cleanup bfq_weights_tree add/remove apis block, bfq: cleanup __bfq_weights_tree_remove() block, bfq: factor out code to update 'active_entities' block, bfq: don't declare 'bfqd' as type 'void *' in bfq_group block, bfq: cleanup bfq_activate_requeue_entity() block, bfq: remove dead code for updating 'rq_in_driver' block/bfq-cgroup.c | 2 +- block/bfq-iosched.c | 38 +++---------------- block/bfq-iosched.h | 11 ++---- block/bfq-wf2q.c | 91 ++++++++++++++++++++------------------------- 4 files changed, 51 insertions(+), 91 deletions(-) -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Yu Kuai <yukuai3@huawei.com> To: jack@suse.cz, axboe@kernel.dk, paolo.valente@linaro.org Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, yukuai3@huawei.com, yi.zhang@huawei.com Subject: [PATCH -next v2 0/6] multiple cleanup patches for bfq Date: Sat, 21 May 2022 15:35:17 +0800 [thread overview] Message-ID: <20220521073523.3118246-1-yukuai3@huawei.com> (raw) Changes in v2: - add missing blank line in patch 1. - remove patch 7,8, since they are wrong. - add reviewed-by tag There are no functional changes in this patchset, just some places that I think can be improved during code review. This patchset is rebased based on this patchset: https://lore.kernel.org/all/20220428120837.3737765-1-yukuai3@huawei.com/ Previous version: v1: https://lore.kernel.org/all/20220514090522.1669270-1-yukuai3@huawei.com/ Yu Kuai (6): block, bfq: cleanup bfq_weights_tree add/remove apis block, bfq: cleanup __bfq_weights_tree_remove() block, bfq: factor out code to update 'active_entities' block, bfq: don't declare 'bfqd' as type 'void *' in bfq_group block, bfq: cleanup bfq_activate_requeue_entity() block, bfq: remove dead code for updating 'rq_in_driver' block/bfq-cgroup.c | 2 +- block/bfq-iosched.c | 38 +++---------------- block/bfq-iosched.h | 11 ++---- block/bfq-wf2q.c | 91 ++++++++++++++++++++------------------------- 4 files changed, 51 insertions(+), 91 deletions(-) -- 2.31.1
next reply other threads:[~2022-05-21 7:21 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-21 7:35 Yu Kuai [this message] 2022-05-21 7:35 ` [PATCH -next v2 0/6] multiple cleanup patches for bfq Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 1/6] block, bfq: cleanup bfq_weights_tree add/remove apis Yu Kuai 2022-05-21 7:35 ` Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 2/6] block, bfq: cleanup __bfq_weights_tree_remove() Yu Kuai 2022-05-21 7:35 ` Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 3/6] block, bfq: factor out code to update 'active_entities' Yu Kuai 2022-05-21 7:35 ` Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 4/6] block, bfq: don't declare 'bfqd' as type 'void *' in bfq_group Yu Kuai 2022-05-21 7:35 ` Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 5/6] block, bfq: cleanup bfq_activate_requeue_entity() Yu Kuai 2022-05-21 7:35 ` Yu Kuai 2022-05-21 7:35 ` [PATCH -next v2 6/6] block, bfq: remove dead code for updating 'rq_in_driver' Yu Kuai 2022-05-21 7:35 ` Yu Kuai
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=20220521073523.3118246-1-yukuai3@huawei.com \ --to=yukuai3@huawei.com \ --cc=axboe@kernel.dk \ --cc=cgroups@vger.kernel.org \ --cc=jack@suse.cz \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=paolo.valente@linaro.org \ --cc=yi.zhang@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: 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.