From: Song Liu <songliubraving@fb.com>
To: Jens Axboe <axboe@kernel.dk>, linux-raid <linux-raid@vger.kernel.org>
Cc: Xiao Ni <xni@redhat.com>, Zhen Lei <thunder.leizhen@huawei.com>,
Yufen Yu <yuyufen@huawei.com>,
Xianting Tian <tian.xianting@h3c.com>
Subject: [GIT PULL] md-next 20200923
Date: Wed, 23 Sep 2020 22:56:49 +0000 [thread overview]
Message-ID: <8960F87F-602B-40B0-863F-E3DE75ACCD45@fb.com> (raw)
Hi Jens,
Please consider pulling the following changes for md-next on top of your
for-5.10/block branch.
Thanks,
Song
The following changes since commit 1fb1a2ad75e33e646d33e42b9ed17d879d472859:
block: mark blkdev_get static (2020-09-23 10:43:19 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/song/md.git md-next
for you to fetch changes up to 10988d55ae96b673332127da4bc3adf5ceb8b370:
md/raid10: Change the return type of raid10_handle_discard to int (2020-09-23 15:42:40 -0700)
----------------------------------------------------------------
Xianting Tian (1):
md: only calculate blocksize once and use i_blocksize()
Xiao Ni (6):
md: add md_submit_discard_bio() for submitting discard bio
md/raid10: extend r10bio devs to raid disks
md/raid10: pull codes that wait for blocked dev into one function
md/raid10: improve raid10 discard request
md/raid10: improve discard request for far layout
md/raid10: Change the return type of raid10_handle_discard to int
Yufen Yu (9):
md/raid5: add a new member of offset into r5dev
md/raid5: make async_copy_data() to support different page offset
md/raid5: add new xor function to support different page offset
md/raid5: convert to new xor compution interface
md/raid6: let syndrome computor support different page offset
md/raid6: let async recovery function support different page offset
md/raid5: let multiple devices of stripe_head share page
md/raid5: resize stripe_head when reshape array
md/raid5: reallocate page array after setting new stripe_size
Zhen Lei (1):
md: Simplify code with existing definition RESYNC_SECTORS in raid10.c
crypto/async_tx/async_pq.c | 72 ++++++++++++++++++++++-----------
crypto/async_tx/async_raid6_recov.c | 163 +++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------
crypto/async_tx/async_xor.c | 120 ++++++++++++++++++++++++++++++++++++++++++++++--------
crypto/async_tx/raid6test.c | 24 +++++++----
drivers/md/md-bitmap.c | 7 ++--
drivers/md/md.c | 20 +++++++++
drivers/md/md.h | 2 +
drivers/md/raid0.c | 14 +------
drivers/md/raid10.c | 431 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------
drivers/md/raid10.h | 1 +
drivers/md/raid5.c | 274 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------
drivers/md/raid5.h | 29 ++++++++++++-
include/linux/async_tx.h | 23 ++++++++---
13 files changed, 967 insertions(+), 213 deletions(-)
next reply other threads:[~2020-09-23 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 22:56 Song Liu [this message]
2020-09-24 19:47 ` [GIT PULL] md-next 20200923 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=8960F87F-602B-40B0-863F-E3DE75ACCD45@fb.com \
--to=songliubraving@fb.com \
--cc=axboe@kernel.dk \
--cc=linux-raid@vger.kernel.org \
--cc=thunder.leizhen@huawei.com \
--cc=tian.xianting@h3c.com \
--cc=xni@redhat.com \
--cc=yuyufen@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).