All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: <qiang.liu@freescale.com>
Cc: arnd@arndb.de, vinod.koul@intel.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, dan.j.williams@gmail.com,
	herbert@gondor.hengli.com.au, linux-crypto@vger.kernel.org,
	dan.j.williams@intel.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 0/8] Raid: enable talitos xor offload for improving performance
Date: Mon, 6 Aug 2012 20:35:06 -0500	[thread overview]
Message-ID: <20120806203506.bcf31cc63a2d1f55a9695f13@freescale.com> (raw)
In-Reply-To: <1344247815-1104-1-git-send-email-qiang.liu@freescale.com>

On Mon, 6 Aug 2012 18:10:15 +0800
<qiang.liu@freescale.com> wrote:

> Changes in v6:
> 	- swap the order of original patch 3/6 and 4/6;
> 	- merge Ira's patch to reduce the size of original patch;
> 	- merge Ira's patch of carma in 8/8;
> 	- update documents and descriptions according to Ira's advice;

fwiw, I gave v5 a test-drive, setting up a RAID5 array on ramdisks
[1], and this patchseries, along with FSL_DMA && NET_DMA set seems
to be holding water, so this series gets my:

Tested-by: Kim Phillips <kim.phillips@freescale.com>

Thanks,

Kim

[1] mdadm --create --verbose --force /dev/md0 --level=raid5 --raid-devices=4 /dev/ram[0123]

WARNING: multiple messages have this Message-ID (diff)
From: Kim Phillips <kim.phillips@freescale.com>
To: <qiang.liu@freescale.com>
Cc: <linux-crypto@vger.kernel.org>, <vinod.koul@intel.com>,
	<dan.j.williams@intel.com>, <herbert@gondor.hengli.com.au>,
	<arnd@arndb.de>, <gregkh@linuxfoundation.org>,
	<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<dan.j.williams@gmail.com>, <leoli@freescale.com>
Subject: Re: [PATCH v6 0/8] Raid: enable talitos xor offload for improving performance
Date: Mon, 6 Aug 2012 20:35:06 -0500	[thread overview]
Message-ID: <20120806203506.bcf31cc63a2d1f55a9695f13@freescale.com> (raw)
In-Reply-To: <1344247815-1104-1-git-send-email-qiang.liu@freescale.com>

On Mon, 6 Aug 2012 18:10:15 +0800
<qiang.liu@freescale.com> wrote:

> Changes in v6:
> 	- swap the order of original patch 3/6 and 4/6;
> 	- merge Ira's patch to reduce the size of original patch;
> 	- merge Ira's patch of carma in 8/8;
> 	- update documents and descriptions according to Ira's advice;

fwiw, I gave v5 a test-drive, setting up a RAID5 array on ramdisks
[1], and this patchseries, along with FSL_DMA && NET_DMA set seems
to be holding water, so this series gets my:

Tested-by: Kim Phillips <kim.phillips@freescale.com>

Thanks,

Kim

[1] mdadm --create --verbose --force /dev/md0 --level=raid5 --raid-devices=4 /dev/ram[0123]


  reply	other threads:[~2012-08-07  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 10:10 [PATCH v6 0/8] Raid: enable talitos xor offload for improving performance qiang.liu
2012-08-06 10:10 ` qiang.liu
2012-08-07  1:35 ` Kim Phillips [this message]
2012-08-07  1:35   ` Kim Phillips
2012-08-07  3:27   ` Liu Qiang-B32616
2012-08-07  3:27     ` Liu Qiang-B32616

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=20120806203506.bcf31cc63a2d1f55a9695f13@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=qiang.liu@freescale.com \
    --cc=vinod.koul@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 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.