linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Code base for rework of ppc440SPe ADMA driver
Date: Wed, 19 Aug 2009 15:49:16 +0200	[thread overview]
Message-ID: <4A8C02DC.8050308@denx.de> (raw)

Hello Dan,

Currently I am trying to estimate efforts for rework of the
ppc440SPe ADMA driver for inclusion in mainline Linux and a couple of
questions have arisen. As the current ASYNC_TX API in mainline Linux
doesn't contain support for RAID6 offload operations, the current
ppc440SPe ADMA driver have to be reworked to support RAID5 operations
only which would be a step backward and also would require some
changes in the ASYNC_TX code to cope with large dma_addr_t addresses.
Therefore my understanding is that the rework of the ADMA driver for
inclusion in mainline should be better based on code from your raid6
branch. Or what would be a better base?

If I understand it correctly initially the intention was to place
this work in linux-next and probably submit a pull request towards
the end of the 2.6.31 merge window. Is there any plan to proceed with
this?  Did you get a chance to look at per-cpu implementation for the
scribble-buffer?

Thanks,
Anatolij

-- 
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

             reply	other threads:[~2009-08-19 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 13:49 Anatolij Gustschin [this message]
2009-08-19 15:35 ` Code base for rework of ppc440SPe ADMA driver Dan Williams

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=4A8C02DC.8050308@denx.de \
    --to=agust@denx.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    /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).