Netdev List
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
	linux-doc@vger.kernel.org, Gary Hook <gary.hook@amd.com>,
	David Howells <dhowells@redhat.com>,
	dm-devel@redhat.com, keyrings@vger.kernel.org,
	linux-ima-devel@lists.sourceforge.net,
	Alasdair Kergon <agk@redhat.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	linux-cifs@vger.kernel.org, linux-ima-user@lists.sourceforge.net,
	Arnaud Ebalard <arno@natisbad.org>,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	James Morris <james.l.morris@oracle.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-arm-kernel@lists.infradead.org, Ofir Dra
Subject: Re: [PATCH v10 00/20] simplify crypto wait for async op
Date: Fri, 3 Nov 2017 22:25:29 +0800	[thread overview]
Message-ID: <20171103142528.GL9011@gondor.apana.org.au> (raw)
In-Reply-To: <1508310057-25369-1-git-send-email-gilad@benyossef.com>

On Wed, Oct 18, 2017 at 08:00:32AM +0100, Gilad Ben-Yossef wrote:
> Many users of kernel async. crypto services have a pattern of
> starting an async. crypto op and than using a completion
> to wait for it to end.
> 
> This patch set simplifies this common use case in two ways:
> 
> First, by separating the return codes of the case where a
> request is queued to a backlog due to the provider being
> busy (-EBUSY) from the case the request has failed due
> to the provider being busy and backlogging is not enabled
> (-ENOSPC).
> 
> Next, this change is than built on to create a generic API
> to wait for a async. crypto operation to complete.
> 
> The end result is a smaller code base and an API that is
> easier to use and more difficult to get wrong.
> 
> The patch set was boot tested on x86_64 and arm64 which
> at the very least tests the crypto users via testmgr and
> tcrypt but I do note that I do not have access to some
> of the HW whose drivers are modified nor do I claim I was
> able to test all of the corner cases.
> 
> The patch set is based upon linux-next release tagged
> next-20171017.

All applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      parent reply	other threads:[~2017-11-03 14:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  7:00 [PATCH v10 00/20] simplify crypto wait for async op Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 01/20] crypto: change transient busy return code to -ENOSPC Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 02/20] crypto: ccp: use -ENOSPC for transient busy indication Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 03/20] net: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 04/20] crypto: remove redundant backlog checks on EBUSY Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 05/20] crypto: marvell/cesa: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 06/20] crypto: introduce crypto wait for async op Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 07/20] crypto: move algif to generic async completion Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 08/20] crypto: move pub key " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 09/20] crypto: move drbg " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 10/20] crypto: move gcm " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 11/20] crypto: move testmgr " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 12/20] fscrypt: move " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 13/20] dm: move dm-verity " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 14/20] cifs: move " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 15/20] ima: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 16/20] crypto: tcrypt: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 17/20] crypto: talitos: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 18/20] crypto: qce: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 19/20] crypto: mediatek: " Gilad Ben-Yossef
2017-10-18  7:00 ` [PATCH v10 20/20] crypto: adapt api sample to use async. op wait Gilad Ben-Yossef
2017-11-03 14:25 ` Herbert Xu [this message]

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=20171103142528.GL9011@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=agk@redhat.com \
    --cc=arno@natisbad.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=gary.hook@amd.com \
    --cc=gilad@benyossef.com \
    --cc=jaegeuk@kernel.org \
    --cc=james.l.morris@oracle.com \
    --cc=keyrings@vger.kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-ima-devel@lists.sourceforge.net \
    --cc=linux-ima-user@lists.sourceforge.net \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=serge@hallyn.com \
    --cc=snitzer@redhat.com \
    --cc=steffen.klassert@secunet.com \
    --cc=thomas.lendacky@amd.com \
    --cc=zohar@linux.vnet.ibm.com \
    /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