Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op

From	Herbert Xu <herbert@gondor.apana.org.au>
Newsgroups	linux.kernel
Subject	Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date	2017-06-10 11:10 +0200
Message-ID	<tQKz7-58R-3@gated-at.bofh.it> (permalink)
References	<tModP-5Cf-5@gated-at.bofh.it> <tModR-5Cf-43@gated-at.bofh.it> <tQFzr-1TZ-7@gated-at.bofh.it> <tQJD4-4zr-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sat, Jun 10, 2017 at 11:05:39AM +0300, Gilad Ben-Yossef wrote:
>
> I guess there is a question if it really is important to know that
> your request ended up
> on the backlog, rather than being handled.I can imagine it can be used
> as back pressure
> indication but I wonder if someone is using that.

Oh yes we do want it to return EBUSY if we put it on the backlog
because in that case we want the user to stop sending us new
requests.

It's the other case where we dropped the request and returned
EBUSY where I think we could return something other than EBUSY
and get rid of the ambiguity.

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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op Herbert Xu <herbert@gondor.apana.org.au> - 2017-06-10 05:50 +0200
  Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op Gilad Ben-Yossef <gilad@benyossef.com> - 2017-06-10 10:10 +0200
    Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op Herbert Xu <herbert@gondor.apana.org.au> - 2017-06-10 11:10 +0200

csiph-web