Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: linux-raid@vger.kernel.org
Cc: neilb@suse.com, shli@fb.com, kernel-team@fb.com,
	dan.j.williams@intel.com, hch@infradead.org,
	liuzhengyuang521@gmail.com, liuzhengyuan@kylinos.cn,
	Song Liu <songliubraving@fb.com>
Subject: [PATCH v3 0/8] raid5-cache: enabling cache features
Date: Thu, 6 Oct 2016 00:14:08 -0700	[thread overview]
Message-ID: <20161006071416.3295093-1-songliubraving@fb.com> (raw)

These are the 3rd version of patches to enable write cache part of
raid5-cache. The journal part was released with kernel 4.4.

The caching part uses same disk format of raid456 journal, and provides
acceleration to writes. Write operations are committed (bio_endio) once
the data is secured in journal. Reconstruct and RMW are postponed to
reclaim path, which is (hopefully) not on the critical path.

The changes are organized in 8 patches (details below).

Patch for chunk_aligned_read in earlier RFC is not included yet
(http://marc.info/?l=linux-raid&m=146432700719277). But we may still need
some optimizations later, especially for SSD raid devices.

Changes from PATCH v2 (http://marc.info/?l=linux-raid&m=147493266208102):
  1. Incorporate feedback from Shaohua
  2. Reorganize the patches, for hopefully easier review
  3. Make sure no change to write through mode (journal only)
  4. Change reclaim design to avoid deadlock due to log space

Thanks,
Song

Song Liu (8):
  md/r5cache: Check array size in r5l_init_log
  md/r5cache: move some code to raid5.h
  md/r5cache: State machine for raid5-cache write back mode
  md/r5cache: write part of r5cache
  md/r5cache: reclaim support
  md/r5cache: sysfs entry r5c_state
  md/r5cache: r5c recovery
  md/r5cache: handle SYNC and FUA

 drivers/md/raid5-cache.c | 1597 ++++++++++++++++++++++++++++++++++++++++------
 drivers/md/raid5.c       |  258 +++++---
 drivers/md/raid5.h       |  150 ++++-
 3 files changed, 1712 insertions(+), 293 deletions(-)

--
2.9.3

             reply	other threads:[~2016-10-06  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  7:14 Song Liu [this message]
2016-10-06  7:14 ` [PATCH v3 1/8] md/r5cache: Check array size in r5l_init_log Song Liu
2016-10-06  7:14 ` [PATCH v3 2/8] md/r5cache: move some code to raid5.h Song Liu
2016-10-06  7:14 ` [PATCH v3 3/8] md/r5cache: State machine for raid5-cache write back mode Song Liu
2016-10-06  7:14 ` [PATCH v3 4/8] md/r5cache: write part of r5cache Song Liu
2016-10-06  7:14 ` [PATCH v3 5/8] md/r5cache: reclaim support Song Liu
2016-10-06  7:14 ` [PATCH v3 6/8] md/r5cache: sysfs entry r5c_state Song Liu
2016-10-06  7:14 ` [PATCH v3 7/8] md/r5cache: r5c recovery Song Liu
2016-10-06  7:14 ` [PATCH v3 8/8] md/r5cache: handle SYNC and FUA Song Liu

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=20161006071416.3295093-1-songliubraving@fb.com \
    --to=songliubraving@fb.com \
    --cc=dan.j.williams@intel.com \
    --cc=hch@infradead.org \
    --cc=kernel-team@fb.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=liuzhengyuan@kylinos.cn \
    --cc=liuzhengyuang521@gmail.com \
    --cc=neilb@suse.com \
    --cc=shli@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