From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
linux-crypto@vger.kernel.org, tmarri@amcc.com
Subject: Re: [PATCH] Adding ADMA support for PPC460EX DMA engine.
Date: Fri, 23 Jul 2010 08:15:14 +0200 [thread overview]
Message-ID: <201007230815.14464.sr@denx.de> (raw)
In-Reply-To: <1279846638-22323-1-git-send-email-tmarri@amcc.com>
Hi Marri,
On Friday 23 July 2010 02:57:18 tmarri@amcc.com wrote:
> From: Tirumala Marri <tmarri@amcc.com>
>
> This patch will add ADMA support for DMA engine and HW offload for
> XOR/ADG (RAID-5/6) functionalities.
> 1. It supports memcpy, xor, GF(2) based RAID-6.
> 2. It supports interrupt based DMA completions.
> 3. Also supports memcpy in RAID-1 case.
>
> Kernel version: 2.6.35-rc5
>
> Testing:
> Created RAID-5/6 arrays usign mdadm.
> And ran raw IO and filesystem IO to the RAID array.
> Chunk size 4k,64k was tested.
> RAID rebuild , disk fail, resync tested.
>
> File names:
> This code is similar to ppc440spe . So I named the files as
> drivers/dma/ppc4xx/adma1.c and drivers/dma/ppc4xx/adma1.h
As you describe above, a lot of the code seems to be copied from
drivers/dma/ppc4xx/adma.c/h. Wouldn't it make more sense to factor out the
common code instead of duplicating it?
Thanks.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office@denx.de
next prev parent reply other threads:[~2010-07-23 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 0:57 [PATCH] Adding ADMA support for PPC460EX DMA engine tmarri
2010-07-23 6:15 ` Stefan Roese [this message]
2010-07-23 19:21 ` Dan Williams
2010-07-23 19:21 ` Dan Williams
2010-07-23 21:39 ` Tirumala Marri
2010-07-23 21:39 ` Tirumala Marri
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=201007230815.14464.sr@denx.de \
--to=sr@denx.de \
--cc=dan.j.williams@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tmarri@amcc.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.