[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B2A6DFA.6000504@intel.com>
Date: Thu, 17 Dec 2009 10:44:26 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Ira W. Snyder" <iws@...o.caltech.edu>
CC: Kumar Gala <galak@...nel.crashing.org>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"B04825@...escale.com" <B04825@...escale.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linuxppc-dev@...abs.org" <linuxppc-dev@...abs.org>,
Vishnu Suresh <Vishnu@...escale.com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
Dipen Dudhat <Dipen.Dudhat@...escale.com>,
Maneesh Gupta <Maneesh.Gupta@...escale.com>,
"R58472@...escale.com" <R58472@...escale.com>
Subject: Re: [PATCH v2 2/2] Crypto: Talitos: Support for Async_tx XOR offload
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists