From: Yu Kuai <yukuai1@huaweicloud.com>
To: song@kernel.org, akpm@osdl.org, neilb@suse.de
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yukuai1@huaweicloud.com, yi.zhang@huawei.com,
yangerkun@huawei.com
Subject: [PATCH -next v2 0/7] limit the number of plugged bio
Date: Wed, 26 Apr 2023 16:20:24 +0800 [thread overview]
Message-ID: <20230426082031.1299149-1-yukuai1@huaweicloud.com> (raw)
From: Yu Kuai <yukuai3@huawei.com>
Changes in v2:
- remove the patch to rename raid1-10.c
This patchset tries to limit the number of plugged bio for raid1 and
raid10, which is done in the last patch, other patches are some refactor
and optimizations.
This patchset is tested with a new test [1], this test triggers dirty
pages writeback for 10s, and in the meantime checks disk inflight.
Before this patchset, test will fail because inflight exceed threshold
(threshold is set to 4096 in the test, in theory this can be mutch
greater as long as there are enough dirty pages and memory).
After this patchset, inflight is within 96 (MAX_PLUG_BIO * copies).
[1] https://lore.kernel.org/linux-raid/20230426073447.1294916-1-yukuai1@huaweicloud.com/
Yu Kuai (7):
md/raid10: prevent soft lockup while flush writes
md/raid1-10: factor out a helper to add bio to plug
md/raid1-10: factor out a helper to submit normal write
md/raid1-10: submit write io directly if bitmap is not enabled
md/md-bitmap: add a new helper to unplug bitmap asynchrously
md/raid1-10: don't handle pluged bio by daemon thread
md/raid1-10: limit the number of plugged bio
drivers/md/md-bitmap.c | 55 +++++++++++++++++++++++++++++++++----
drivers/md/md-bitmap.h | 10 +++++++
drivers/md/raid1-10.c | 62 ++++++++++++++++++++++++++++++++++++++++++
drivers/md/raid1.c | 29 ++++----------------
drivers/md/raid10.c | 47 +++++++-------------------------
5 files changed, 136 insertions(+), 67 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-26 8:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 8:20 Yu Kuai [this message]
2023-04-26 8:20 ` [PATCH -next v2 1/7] md/raid10: prevent soft lockup while flush writes Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 2/7] md/raid1-10: factor out a helper to add bio to plug Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 3/7] md/raid1-10: factor out a helper to submit normal write Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 4/7] md/raid1-10: submit write io directly if bitmap is not enabled Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 5/7] md/md-bitmap: add a new helper to unplug bitmap asynchrously Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 6/7] md/raid1-10: don't handle pluged bio by daemon thread Yu Kuai
2023-04-26 8:20 ` [PATCH -next v2 7/7] md/raid1-10: limit the number of plugged bio Yu Kuai
2023-05-29 2:08 ` Xiao Ni
2023-05-29 2:19 ` Yu Kuai
2023-05-29 3:10 ` Xiao Ni
2023-05-29 3:18 ` Yu Kuai
2023-05-29 7:57 ` Xiao Ni
2023-05-29 8:50 ` Yu Kuai
2023-05-30 0:58 ` Xiao Ni
2023-05-30 1:19 ` Yu Kuai
2023-05-30 2:25 ` Xiao Ni
2023-05-12 9:42 ` [PATCH -next v2 0/7] " Yu Kuai
2023-05-13 0:50 ` Song Liu
2023-05-13 2:03 ` 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=20230426082031.1299149-1-yukuai1@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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: 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 NNTP newsgroup(s).