From: Shaohua Li <shli@kernel.org>
To: Song Liu <songliubraving@fb.com>
Cc: linux-raid@vger.kernel.org, neilb@suse.com, shli@fb.com,
kernel-team@fb.com, dan.j.williams@intel.com, hch@infradead.org,
liuzhengyuang521@gmail.com, liuzhengyuan@kylinos.cn
Subject: Re: [PATCH v4 0/8] raid5-cache: enabling cache features
Date: Wed, 12 Oct 2016 10:52:02 -0700 [thread overview]
Message-ID: <20161012175202.GA58645@kernel.org> (raw)
In-Reply-To: <20161011002446.2002428-1-songliubraving@fb.com>
On Mon, Oct 10, 2016 at 05:24:38PM -0700, Song Liu wrote:
> These are the 4th 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 v3 (http://marc.info/?l=linux-raid&m=147573807306070):
> 1. Make reclaim robust
> 2. Fix a bug in recovery
>
> Changes between v3 and 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
Could you please add a test case for this in mdadm test suites?
Thanks,
Shaohua
prev parent reply other threads:[~2016-10-12 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 0:24 [PATCH v4 0/8] raid5-cache: enabling cache features Song Liu
2016-10-11 0:24 ` [PATCH v4 1/8] md/r5cache: Check array size in r5l_init_log Song Liu
2016-10-11 0:24 ` [PATCH v4 2/8] md/r5cache: move some code to raid5.h Song Liu
2016-10-11 0:24 ` [PATCH v4 3/8] md/r5cache: State machine for raid5-cache write back mode Song Liu
2016-10-11 0:24 ` [PATCH v4 4/8] md/r5cache: write part of r5cache Song Liu
2016-10-11 0:24 ` [PATCH v4 5/8] md/r5cache: reclaim support Song Liu
2016-10-12 16:50 ` Shaohua Li
2016-10-11 0:24 ` [PATCH v4 6/8] md/r5cache: sysfs entry r5c_state Song Liu
2016-10-12 16:56 ` Shaohua Li
2016-10-12 21:23 ` Song Liu
2016-10-11 0:24 ` [PATCH v4 7/8] md/r5cache: r5c recovery Song Liu
2016-10-11 0:24 ` [PATCH v4 8/8] md/r5cache: handle SYNC and FUA Song Liu
2016-10-12 17:52 ` Shaohua Li [this message]
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=20161012175202.GA58645@kernel.org \
--to=shli@kernel.org \
--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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.