Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
To: ext Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: crypto_shash_update & CRYPTO_TFM_REQ_MAY_SLEEP
Date: Tue, 16 Feb 2010 09:05:10 +0200	[thread overview]
Message-ID: <4B7A43A6.6090409@nokia.com> (raw)
In-Reply-To: <20100216065844.GA28436@gondor.apana.org.au>

Hi,

How is it possible to wait for completion here?: shash.c

shash_compat_digest()
{
....
        data = crypto_kmap(sg_page(sg), 0);
        err = crypto_shash_digest(desc, data + offset, nbytes, out);
        crypto_kunmap(data, 0);
....
}

It happens as single operation/call.

Thanks,
Dmitry


ext Herbert Xu wrote:
> On Tue, Feb 16, 2010 at 08:36:08AM +0200, Dmitry Kasatkin wrote:
>   
>> Hi,
>>
>> we have HW accelerator which can be accessed without DMA.
>> CPU just sequentially writes data to the port and then reads result.
>>     
>
> Well if that's the case then you definitely don't need anything
> other than kmap_atomic.  You should be able to map it atomically,
> write the data out, unmap it, and then wait for the completion.
>
> Non-atomic kmaps should be avoided if at all possible.
>
> Cheers,
>   

  reply	other threads:[~2010-02-16  7:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 17:21 crypto_shash_update & CRYPTO_TFM_REQ_MAY_SLEEP Dmitry Kasatkin
2010-02-09  7:41 ` Herbert Xu
2010-02-09  8:45   ` Dmitry Kasatkin
2010-02-09  9:02     ` Herbert Xu
2010-02-10 12:16   ` Dmitry Kasatkin
2010-02-15 19:20     ` Dmitry Kasatkin
2010-02-16  0:44       ` Herbert Xu
2010-02-16  6:36         ` Dmitry Kasatkin
2010-02-16  6:58           ` Herbert Xu
2010-02-16  7:05             ` Dmitry Kasatkin [this message]
2010-02-16  7:27               ` Herbert Xu

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=4B7A43A6.6090409@nokia.com \
    --to=dmitry.kasatkin@nokia.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.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