Thread (5 messages) 5 messages, 3 authors, 2007-07-12

Re: [RFC 1/2] SPU-AES support (kernel side)

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: 2007-07-12 04:36:15

On Wed, Jun 27, 2007 at 01:00:27AM +0200, Sebastian Siewior wrote:
+static int enqueue_request(struct ablkcipher_request *req,
+		enum SPU_FUNCTIONS op_type)
+{
+	struct async_d_request *asy_d_ctx = ablkcipher_request_ctx(req);
+	struct crypto_ablkcipher *tfm = crypto_ablkcipher_reqtfm(req);
+	struct aes_ctx *ctx = crypto_ablkcipher_ctx(tfm);
+	struct kspu_work_item *work = &asy_d_ctx->kspu_work;
+
+	asy_d_ctx->crypto_operation = op_type;
+	asy_d_ctx->progress = 0;
+	work->enqueue = aes_queue_work_items;
+
+	kspu_enqueue_work_item(ctx->spe_ctx->ctx, &asy_d_ctx->kspu_work);
OK this is a software queue so we want to put a limit on it.
In fact, any reason why you couldn't juse use the existing
crypto_enqueue_request interface here? That would also make
that cast function unnecessary.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} [off-list ref]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help