From: Shaohua Li <shli@fb.com>
To: linux-raid@vger.kernel.org
Cc: Kernel-team@fb.com, songliubraving@fb.com, hch@infradead.org,
dan.j.williams@intel.com, neilb@suse.de
Subject: [PATCH 0/8] raid5-cache fixes
Date: Wed, 2 Sep 2015 13:49:43 -0700 [thread overview]
Message-ID: <cover.1441221530.git.shli@fb.com> (raw)
Fix some bugs, improve performance and add trim/resync support.
Thanks,
Shaohua
Christoph Hellwig (1):
raid5-cache: move functionality out of __r5l_set_io_unit_state
Shaohua Li (7):
md: fix feature map check
raid5: fix build error
raid5-cache: switching to state machine for log disk cache flush
raid5-cache: fix a user-after-free bug
raid5-cache: optimize FLUSH IO with log enabled
md: skip resync for raid array with journal
raid5-cache: add trim support for log
drivers/md/md.c | 6 +-
drivers/md/md.h | 1 +
drivers/md/raid5-cache.c | 254 ++++++++++++++++++++++++++++-------------------
drivers/md/raid5.c | 17 +++-
drivers/md/raid5.h | 1 +
5 files changed, 175 insertions(+), 104 deletions(-)
--
1.8.1
next reply other threads:[~2015-09-02 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 20:49 Shaohua Li [this message]
2015-09-02 20:49 ` [PATCH 1/8] md: fix feature map check Shaohua Li
2015-09-02 20:49 ` [PATCH 2/8] raid5: fix build error Shaohua Li
2015-09-02 20:49 ` [PATCH 3/8] raid5-cache: switching to state machine for log disk cache flush Shaohua Li
2015-09-02 20:49 ` [PATCH 4/8] raid5-cache: fix a user-after-free bug Shaohua Li
2015-09-02 20:49 ` [PATCH 5/8] raid5-cache: move functionality out of __r5l_set_io_unit_state Shaohua Li
2015-09-02 20:49 ` [PATCH 6/8] raid5-cache: optimize FLUSH IO with log enabled Shaohua Li
2015-09-02 20:49 ` [PATCH 7/8] md: skip resync for raid array with journal Shaohua Li
2015-09-30 4:24 ` Neil Brown
2015-10-01 17:47 ` Song Liu
2015-10-01 23:50 ` Neil Brown
2015-09-02 20:49 ` [PATCH 8/8] raid5-cache: add trim support for log Shaohua Li
2015-09-30 4:14 ` Neil Brown
2015-09-30 5:36 ` [PATCH 0/8] raid5-cache fixes Neil Brown
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=cover.1441221530.git.shli@fb.com \
--to=shli@fb.com \
--cc=Kernel-team@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=songliubraving@fb.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).