linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@intel.com>
Cc: linux-raid@vger.kernel.org, wojciech.neubauer@intel.com,
	adam.kwolek@intel.com, dan.j.williams@intel.com,
	ed.ciechanowski@intel.com
Subject: Re: [PATCH 0/5] imsm support for raid0->raid5 migration
Date: Mon, 9 May 2011 12:03:28 +1000	[thread overview]
Message-ID: <20110509120328.75e5b2a7@notabene.brown> (raw)
In-Reply-To: <20110504151011.24386.14976.stgit@gklab-128-081.igk.intel.com>

On Wed, 04 May 2011 17:10:33 +0200 Przemyslaw Czarnowski
<przemyslaw.hawrylewicz.czarnowski@intel.com> wrote:

> Migration r0->r5 once again; with a fix comming from your comment.
> 
> The following series implements support for raid0->raid5 migration for IMSM
> metadata. These patches blocks opposite direction of migration.
> Code mostly bases on patches sent to you by Adam Kwolek. I have incorporated
> your remarks and I tested it quite extensively for comformity with IMSM
> standard. I have also removed opposite direction, as it is just not supported
> right now.
> 
> Note:
> Please do not include these patches on 'master' branch, as they are supposed
> to be a part of next minor mdadm version (ie. mdadm 3.2.2). I think good place
> for it is devel-3.2. Master should be reserved just for bug/stability fixes
> for previous release.

I have applied these patches, and in fact I have applied them to 'master'
because that if where I think they belong.  Eventually 3.2.2 will be whatever
is on 'master' at that time.

I might create a devel-3.3 at some stage to do some brand new development,
but these patches are just a continuation of what went into 3.2 and 3.2.1 so
I think this is where they belong.

Thanks,
NeilBrown

> ---
> 
> Przemyslaw Czarnowski (5):
>       imsm: prepare update for level migrations reshape
>       imsm: fix: disable migration from raid5->raid0
>       imsm: prepare memory for level migration update
>       imsm: process update for raid level migrations
>       imsm: add new chunk size to metadata update
> 
> 
>  super-intel.c |  337 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  1 files changed, 330 insertions(+), 7 deletions(-)
> 


      parent reply	other threads:[~2011-05-09  2:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 15:10 [PATCH 0/5] imsm support for raid0->raid5 migration Przemyslaw Czarnowski
2011-05-04 15:11 ` [PATCH 1/5] imsm: prepare update for level migrations reshape Przemyslaw Czarnowski
2011-05-04 15:11 ` [PATCH 2/5] imsm: fix: disable migration from raid5->raid0 Przemyslaw Czarnowski
2011-05-04 15:12 ` [PATCH 3/5] imsm: prepare memory for level migration update Przemyslaw Czarnowski
2011-05-04 15:12 ` [PATCH 4/5] imsm: process update for raid level migrations Przemyslaw Czarnowski
2011-05-04 15:13 ` [PATCH 5/5] imsm: add new chunk size to metadata update Przemyslaw Czarnowski
2011-05-09  2:03 ` NeilBrown [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=20110509120328.75e5b2a7@notabene.brown \
    --to=neilb@suse.de \
    --cc=adam.kwolek@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
    --cc=wojciech.neubauer@intel.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).