From: Dan Williams <dan.j.williams@intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"B04825@freescale.com" <B04825@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Vishnu Suresh <Vishnu@freescale.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Dipen Dudhat <Dipen.Dudhat@freescale.com>,
Maneesh Gupta <Maneesh.Gupta@freescale.com>,
"R58472@freescale.com" <R58472@freescale.com>
Subject: Re: [PATCH v2 2/2] Crypto: Talitos: Support for Async_tx XOR offload
Date: Wed, 16 Dec 2009 15:47:48 -0700 [thread overview]
Message-ID: <4B296394.9010709@intel.com> (raw)
In-Reply-To: <2868C8CF-584B-4FA7-9C3B-2FACEF77527E@kernel.crashing.org>
Kumar Gala wrote:
>>> Changes with respect to v1 as per comments received
>>> o. Rebased to linux-next as of 20091216
>>> o. The selection is based exclusive of fsldma
>>> o. Intoduced a new Kernel Configuration variable
>>> *. This enables selecting the Cryptographic functionality
>>> of Talitos along with fsldma.
>>> *. Disables the XOR parity calculation offload, if fsldma enabled
>>> either as kernel in-built or as a module
>>> *. Once the inter-operability with fsldma is resolved, this option
>>> can be removed
>> wait, why can't the interoperability bug be fixed in the first place?
>
> I agree w/Kim. We need to better understand what the bug is and how to reproduce it so we can get to the root cause.
>
> Paper taping over it by disabling fsldma is not the right solution.
Hopefully this prompts fsldma authors to get involved because the
interoperability issue has been out there without comment*, just
band-aids, since October.
--
Dan
* well one comment from Ira saying the interrupt functionality worked
for him.
next prev parent reply other threads:[~2009-12-16 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 15:34 [PATCH v2 2/2] Crypto: Talitos: Support for Async_tx XOR offload Vishnu Suresh
2009-12-16 22:41 ` Kim Phillips
2009-12-16 22:38 ` Kumar Gala
2009-12-16 22:47 ` Dan Williams [this message]
2009-12-17 17:09 ` Ira W. Snyder
2009-12-17 17:29 ` Kumar Gala
2009-12-17 17:44 ` Dan Williams
2009-12-17 18:45 ` Kumar Gala
2009-12-18 0:58 ` Dan Williams
2009-12-18 15:02 ` Li Yang-R58472
2009-12-18 22:17 ` Dan Williams
2009-12-26 21:41 ` Ira W. Snyder
2009-12-18 14:46 ` Li Yang-R58472
2010-07-14 3:58 ` hank peng
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=4B296394.9010709@intel.com \
--to=dan.j.williams@intel.com \
--cc=B04825@freescale.com \
--cc=Dipen.Dudhat@freescale.com \
--cc=Maneesh.Gupta@freescale.com \
--cc=R58472@freescale.com \
--cc=Vishnu@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).