linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Kasatkin <dmitry.kasatkin@nokia.com>
To: ext Herbert Xu <herbert@gondor.hengli.com.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver
Date: Fri, 16 Apr 2010 10:44:37 +0300	[thread overview]
Message-ID: <4BC81565.8040808@nokia.com> (raw)
In-Reply-To: <20100414065500.GA20713@gondor.apana.org.au>

Hi,

crypto_ahash_update()
crypto_ahash_dinup()
crypto_ahash_final()

obviously might need to return -EINPROGRESS

but can
crypto_ahash_init(req)

be synchronous?

Or it could also return EINPROGRESS, though not sense.

- Dmitry


On 14/04/10 09:55, ext Herbert Xu wrote:
> On Wed, Apr 14, 2010 at 09:51:22AM +0300, Dmitry Kasatkin wrote:
>    
>> What do you mean by "merge operation".
>> request merging?
>>      
> By buffering user data, you're in essence merging requests.
>
> I have no objections to doing that, but let's not do it in every
> driver.
>
> Of course, the ultimate solution is for the end-user to produce
> requests that do not need merging.  So when considering this we
> need to be aware of what users are being targeted.
>
> Thanks,
>    

  reply	other threads:[~2010-04-16  7:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 16:35 [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 & MD5 driver Dmitry.Kasatkin
2010-04-13  8:59 ` Herbert Xu
2010-04-13  9:39   ` Dmitry Kasatkin
2010-04-13 10:03     ` Herbert Xu
2010-04-13 10:13       ` Dmitry Kasatkin
2010-04-13 12:02         ` Herbert Xu
2010-04-13 13:00           ` Dmitry Kasatkin
2010-04-13 14:45             ` Herbert Xu
2010-04-13 15:16               ` Uri Simchoni
2010-04-13 15:21                 ` Dmitry Kasatkin
2010-04-14  0:44                   ` Herbert Xu
2010-04-14  6:37                     ` Dmitry Kasatkin
2010-04-14  6:44                       ` Herbert Xu
2010-04-14  6:51                         ` Dmitry Kasatkin
2010-04-14  6:55                           ` Herbert Xu
2010-04-16  7:44                             ` Dmitry Kasatkin [this message]
2010-04-19 13:27                               ` Herbert Xu
2010-04-13 10:15       ` Dmitry Kasatkin
2010-04-13 12:00         ` Uri Simchoni
2010-04-13 12:10         ` Herbert Xu
2010-04-13 13:44           ` Dmitry Kasatkin
2010-04-13 14:36             ` Dmitry Kasatkin
2010-04-13 14:42               ` Herbert Xu
2010-04-13 15:33                 ` Dmitry Kasatkin
2010-04-14  0:47                   ` Herbert Xu
2010-04-13 14:48             ` Herbert Xu
2010-04-13 15:48               ` Dmitry Kasatkin
2010-04-14  0:50                 ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2010-03-17 13:12 Dmitry Kasatkin
2010-03-23 11:32 ` Herbert Xu
2010-03-24  7:31   ` Dmitry Kasatkin
2010-03-24 14:51   ` Dmitry Kasatkin
2010-04-08 14:07     ` Herbert Xu
2010-04-08 14:04   ` 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=4BC81565.8040808@nokia.com \
    --to=dmitry.kasatkin@nokia.com \
    --cc=herbert@gondor.hengli.com.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;
as well as URLs for NNTP newsgroup(s).