From: Yu Kuai <yukuai3@huawei.com> To: <paolo.valente@linaro.org>, <jack@suse.cz>, <axboe@kernel.dk> Cc: <linux-block@vger.kernel.org>, <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <yukuai3@huawei.com>, <yi.zhang@huawei.com> Subject: [PATCH v3 0/3] block, bfq: minor cleanup and fix Date: Sat, 29 Jan 2022 09:59:21 +0800 [thread overview] Message-ID: <20220129015924.3958918-1-yukuai3@huawei.com> (raw) Changes in v3: - fix a clerical error in patch 2 Chagnes in v2: - add comment in patch 2 - remove patch 4, since the problem do not exist. Yu Kuai (3): block, bfq: cleanup bfq_bfqq_to_bfqg() block, bfq: avoid moving bfqq to it's parent bfqg block, bfq: don't move oom_bfqq block/bfq-cgroup.c | 16 +++++++++++++++- block/bfq-iosched.c | 4 ++-- block/bfq-iosched.h | 1 - block/bfq-wf2q.c | 15 --------------- 4 files changed, 17 insertions(+), 19 deletions(-) -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Yu Kuai <yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> To: paolo.valente-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, jack-AlSwsSmVLrQ@public.gmane.org, axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org Cc: linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org, yi.zhang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org Subject: [PATCH v3 0/3] block, bfq: minor cleanup and fix Date: Sat, 29 Jan 2022 09:59:21 +0800 [thread overview] Message-ID: <20220129015924.3958918-1-yukuai3@huawei.com> (raw) Changes in v3: - fix a clerical error in patch 2 Chagnes in v2: - add comment in patch 2 - remove patch 4, since the problem do not exist. Yu Kuai (3): block, bfq: cleanup bfq_bfqq_to_bfqg() block, bfq: avoid moving bfqq to it's parent bfqg block, bfq: don't move oom_bfqq block/bfq-cgroup.c | 16 +++++++++++++++- block/bfq-iosched.c | 4 ++-- block/bfq-iosched.h | 1 - block/bfq-wf2q.c | 15 --------------- 4 files changed, 17 insertions(+), 19 deletions(-) -- 2.31.1
next reply other threads:[~2022-01-29 1:48 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-29 1:59 Yu Kuai [this message] 2022-01-29 1:59 ` [PATCH v3 0/3] block, bfq: minor cleanup and fix Yu Kuai 2022-01-29 1:51 ` Jens Axboe 2022-01-29 1:51 ` Jens Axboe 2022-01-29 2:05 ` yukuai (C) 2022-01-29 2:05 ` yukuai (C) 2022-02-10 11:46 ` yukuai (C) 2022-02-10 11:46 ` yukuai (C) 2022-02-18 8:30 ` yukuai (C) 2022-02-18 8:30 ` yukuai (C) 2022-01-29 1:59 ` [PATCH v3 1/3] block, bfq: cleanup bfq_bfqq_to_bfqg() Yu Kuai 2022-01-29 1:59 ` Yu Kuai 2022-01-29 1:59 ` [PATCH v3 2/3] block, bfq: avoid moving bfqq to it's parent bfqg Yu Kuai 2022-01-29 1:59 ` Yu Kuai 2022-02-08 3:53 ` yukuai (C) 2022-02-08 3:53 ` yukuai (C) 2022-02-08 16:07 ` Paolo Valente 2022-02-08 16:07 ` Paolo Valente 2022-01-29 1:59 ` [PATCH v3 3/3] block, bfq: don't move oom_bfqq Yu Kuai 2022-01-29 1:59 ` Yu Kuai 2022-02-18 13:13 ` [PATCH v3 0/3] block, bfq: minor cleanup and fix 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=20220129015924.3958918-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.