[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3A45394FD742FA419B760BB8D398F9ED01059526@zch01exm26.fsl.freescale.net>
Date: Fri, 18 Dec 2009 23:02:22 +0800
From: "Li Yang-R58472" <r58472@...escale.com>
To: "Dan Williams" <dan.j.williams@...el.com>,
"Ira W. Snyder" <iws@...o.caltech.edu>
Cc: "Kumar Gala" <galak@...nel.crashing.org>,
<herbert@...dor.apana.org.au>,
"Tabi Timur-B04825" <B04825@...escale.com>,
<linux-kernel@...r.kernel.org>, <linux-raid@...r.kernel.org>,
<linuxppc-dev@...abs.org>,
"Suresh Vishnu-B05022" <B05022@...escale.com>,
<linux-crypto@...r.kernel.org>,
"Dudhat Dipen-B09055" <B09055@...escale.com>,
"Gupta Maneesh-B18878" <B18878@...escale.com>
Subject: RE: [PATCH v2 2/2] Crypto: Talitos: Support for Async_tx XOR offload
>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.
I am wondering if can use more callbacks to kick off pending dependent operations?
Like xor->callback->copy->callback->xor->callback?
- Leo
--
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