From: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
To: Shaohua Li <shli@fb.com>, 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: Re: [PATCH v2 0/6] a caching layer for raid5/6
Date: Tue, 19 May 2015 11:22:51 +0200 [thread overview]
Message-ID: <555B00EB.9040303@intel.com> (raw)
In-Reply-To: <cover.1432003804.git.shli@fb.com>
On 05/19/2015 04:57 AM, Shaohua Li wrote:
> Hi,
>
> This is the second version of the raid5/6 caching layer patches. The patches add a
> caching layer for raid5/6. The caching layer uses a SSD as a cache for a raid
> 5/6. It works like the similar way of a hardware raid controller. The purpose
> is to improve raid performance (reduce read-modify-write) and fix write hole
> issue. The main patch is patch 3 and the description has all details about the
> implementation.
>
> Main changes of V2 are to improve performance. Meta data write doesn't use FUA
> any more. Discard request is only dispatched when discard range is big enough.
> Also have some bug fixing and code cleanup. Please review!
Hi,
It seems patch 3 is missing.
Artur
next prev parent reply other threads:[~2015-05-19 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 2:57 [PATCH v2 0/6] a caching layer for raid5/6 Shaohua Li
2015-05-19 2:57 ` [PATCH v2 1/6] MD: add a new disk role to present cache device Shaohua Li
2015-05-19 2:57 ` [PATCH v2 2/6] raid5: directly use mddev->queue Shaohua Li
2015-05-19 2:57 ` [PATCH v2 4/6] raid5: add some sysfs entries Shaohua Li
2015-05-19 2:57 ` [PATCH v2 5/6] md: don't allow resize/reshape with cache support Shaohua Li
2015-05-19 2:57 ` [PATCH v2 6/6] raid5: skip resync if caching is enabled Shaohua Li
2015-05-19 9:22 ` Artur Paszkiewicz [this message]
2015-05-20 5:23 ` [PATCH v2 0/6] a caching layer for raid5/6 NeilBrown
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=555B00EB.9040303@intel.com \
--to=artur.paszkiewicz@intel.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=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 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).