From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [1/1 take 2] HIFN: preliminary HIFN 795x driver for new async cryptoapi.
Date: Fri, 22 Jun 2007 15:57:26 +0400 [thread overview]
Message-ID: <20070622115726.GA29425@2ka.mipt.ru> (raw)
In-Reply-To: <20070622072844.GA27341@gondor.apana.org.au>
Hi Herbert.
On Fri, Jun 22, 2007 at 03:28:44PM +0800, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> > + * Actually I need to think about how to handle the case, when queue is full.
> > + * So far error (-EINVAL) is returned.
> > + */
>
> OK you need to provide a software queue here. Since you already
> have a hardware queue, you may choose to have a queue with a
> (advisory) maximum length of zero. However, a queue is still
> necessary since requests with the MAY_BACKLOG flag must never
> be discarded.
>
> This is (or will be) used by users such as dm-crypt that must be
> able to add at least one request but can throttle themselves
> afterwards .
What will prevent crypto user from filling that queue with crypto
requests more and more when hardware is not capable to work with such
rate?
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-06-22 11:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:42 [1/1 take 2] HIFN: preliminary HIFN 795x driver for new async cryptoapi Evgeniy Polyakov
2007-06-05 12:56 ` Sebastian Siewior
2007-06-05 13:07 ` Evgeniy Polyakov
2007-06-05 15:02 ` Evgeniy Polyakov
2007-06-22 7:34 ` Herbert Xu
2007-06-22 11:58 ` Evgeniy Polyakov
2007-06-22 12:37 ` Herbert Xu
2007-06-22 13:32 ` Evgeniy Polyakov
2007-06-09 5:02 ` Herbert Xu
2007-06-22 7:28 ` Herbert Xu
2007-06-22 11:57 ` Evgeniy Polyakov [this message]
2007-06-22 12:29 ` Sebastian Siewior
2007-06-22 12:36 ` Herbert Xu
2007-06-22 12:39 ` Evgeniy Polyakov
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=20070622115726.GA29425@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--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