From: Dan Williams <dan.j.williams@intel.com>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
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: Thu, 17 Dec 2009 10:44:26 -0700 [thread overview]
Message-ID: <4B2A6DFA.6000504@intel.com> (raw)
In-Reply-To: <20091217170958.GE18271@ovro.caltech.edu>
Ira W. Snyder wrote:
> Yes, I have used the device_prep_dma_interrupt() functionality quite a
> while back. However, I found it to be pretty much useless.
The specific case it is needed for Talitos/raid is a channel switch
interrupt. The interrupt causes the cleanup operation to be run which
will kick off any pending dependent operations on the xor channel. In
the raid case we only have callbacks at the end of a chain, so we need
the interrupt to kick the engine in an operation chain like
xor->copy->xor->callback.
--
Dan
next prev parent reply other threads:[~2009-12-17 17:44 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
2009-12-17 17:09 ` Ira W. Snyder
2009-12-17 17:29 ` Kumar Gala
2009-12-17 17:44 ` Dan Williams [this message]
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=4B2A6DFA.6000504@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=herbert@gondor.apana.org.au \
--cc=iws@ovro.caltech.edu \
--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).