From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org,
Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Subject: Re: [1/1 take 2] HIFN 795x driver.
Date: Thu, 4 Oct 2007 13:22:20 +0400 [thread overview]
Message-ID: <20071004092218.GA23613@2ka.mipt.ru> (raw)
In-Reply-To: <20071004054923.GA16226@gondor.apana.org.au>
On Thu, Oct 04, 2007 at 01:49:23PM +0800, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> > What is may backlog option? I did not find it in cryptd.c, which I used
> > for reference. I found a backlog variables in the driver, but without
> > any signs for the outside world - queue is initialized and backlog is
> > being set to that queue - since there is a dequeueing code, what is a
> > purpose for backlog in that case?
>
> It's not directly in cryptd because it uses the helpers from
> algapi.c. In particular ablkcipher_enqueue_request has the
> necessary logic to handle this correctly.
>
> You could either use that helper yourself once your hardware
> queue fills up, or implement your own backlog logic. The key
> is each tfm object must be guaranteed to be able to queue at
> least one request.
I use ablkcipher_enqueue_request() when hardware can not handle new
request, so this should be ok.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-10-04 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 15:00 [1/1 take 2] HIFN 795x driver Evgeniy Polyakov
2007-10-02 19:05 ` Sebastian Siewior
2007-10-03 8:41 ` Evgeniy Polyakov
2007-10-03 11:54 ` Herbert Xu
2007-10-03 12:05 ` Evgeniy Polyakov
2007-10-04 5:49 ` Herbert Xu
2007-10-04 9:22 ` Evgeniy Polyakov [this message]
2007-10-04 10:04 ` Herbert Xu
2007-10-04 15:04 ` Evgeniy Polyakov
2007-10-05 8:18 ` Herbert Xu
2007-10-06 21:58 ` Sebastian Siewior
2007-10-08 3:15 ` Herbert Xu
2007-10-08 15:49 ` Sebastian Siewior
2007-10-08 16:07 ` 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=20071004092218.GA23613@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--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