From: Song Liu <songliubraving@meta.com>
To: Jens Axboe <axboe@kernel.dk>, linux-raid <linux-raid@vger.kernel.org>
Cc: Yu Kuai <yukuai1@huaweicloud.com>, Yu Kuai <yukuai3@huawei.com>,
Heming Zhao <heming.zhao@suse.com>, Li Nan <linan122@huawei.com>,
Paul Luse <paul.e.luse@linux.intel.com>
Subject: [GIT PULL] md-6.9 20240301
Date: Fri, 1 Mar 2024 07:44:33 +0000 [thread overview]
Message-ID: <B6EB79F8-7936-49A6-940A-0053DE38AB20@fb.com> (raw)
Hi Jens,
Please consider pulling the following changes for md-6.9 on top of your
for-6.9/block branch. The major changes are:
1. Refactor raid1 read_balance, by Yu Kuai and Paul Luse.
2. Clean up and fix for md_ioctl, by Li Nan.
3. Other small fixes, by Gui-Dong Han and Heming Zhao.
Thanks,
Song
The following changes since commit 82c6515d8a970f471eeb8a5ceeaa04c3e5e1b45c:
bdev: remove SLAB_MEM_SPREAD flag usage (2024-02-24 13:16:08 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git tags/md-6.9-20240301
for you to fetch changes up to e81faa91a580cd151e3e88816786e0c270cefb98:
Merge branch 'raid1-read_balance' into md-6.9 (2024-02-29 22:50:26 -0800)
----------------------------------------------------------------
Gui-Dong Han (1):
md/raid5: fix atomicity violation in raid5_cache_count
Heming Zhao (1):
md/md-bitmap: fix incorrect usage for sb_index
Li Nan (9):
md: merge the check of capabilities into md_ioctl_valid()
md: changed the switch of RAID_VERSION to if
md: clean up invalid BUG_ON in md_ioctl
md: return directly before setting did_set_md_closing
md: Don't clear MD_CLOSING when the raid is about to stop
md: factor out a helper to sync mddev
md: sync blockdev before stopping raid or setting readonly
md: clean up openers check in do_md_stop() and md_set_readonly()
md: check mddev->pers before calling md_set_readonly()
Song Liu (1):
Merge branch 'raid1-read_balance' into md-6.9
Yu Kuai (11):
md: add a new helper rdev_has_badblock()
md/raid1: factor out helpers to add rdev to conf
md/raid1: record nonrot rdevs while adding/removing rdevs to conf
md/raid1: fix choose next idle in read_balance()
md/raid1-10: add a helper raid1_check_read_range()
md/raid1-10: factor out a new helper raid1_should_read_first()
md/raid1: factor out read_first_rdev() from read_balance()
md/raid1: factor out choose_slow_rdev() from read_balance()
md/raid1: factor out choose_bb_rdev() from read_balance()
md/raid1: factor out the code to manage sequential IO
md/raid1: factor out helpers to choose the best rdev from read_balance()
drivers/md/md-bitmap.c | 9 +-
drivers/md/md.c | 183 ++++++++++++-----------
drivers/md/md.h | 11 ++
drivers/md/raid1-10.c | 69 +++++++++
drivers/md/raid1.c | 550 ++++++++++++++++++++++++++++++++++++++++++----------------------------
drivers/md/raid1.h | 1 +
drivers/md/raid10.c | 58 +++-----
drivers/md/raid5.c | 49 +++----
8 files changed, 549 insertions(+), 381 deletions(-)
next reply other threads:[~2024-03-01 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 7:44 Song Liu [this message]
2024-03-01 12:37 ` [GIT PULL] md-6.9 20240301 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=B6EB79F8-7936-49A6-940A-0053DE38AB20@fb.com \
--to=songliubraving@meta.com \
--cc=axboe@kernel.dk \
--cc=heming.zhao@suse.com \
--cc=linan122@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=paul.e.luse@linux.intel.com \
--cc=yukuai1@huaweicloud.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 read-only IMAP folder(s) and NNTP newsgroup(s).