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, David Howells <dhowells@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
keyrings@vger.kernel.org, linux-ima-devel@lists.sourceforge.net,
Pavel Shilovsky <pshilov@microsoft.com>,
Alasdair Kergon <agk@redhat.com>,
linux-cifs@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-ima-user@lists.sourceforge.net,
Eric Biggers <ebiggers3@gmail.com>,
linux-raid@vger.kernel.org, linux-fscrypt@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Ofir Drang <ofir.drang@arm.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
samba-technical@lists.samba.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Steve French <sfrench@samba.org>, linux-
Subject: Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date: Sat, 10 Jun 2017 17:01:31 +0800 [thread overview]
Message-ID: <20170610090131.GA15594@gondor.apana.org.au> (raw)
In-Reply-To: <CAOtvUMeRtcVcp8HE9oJAkJO35yF9XBsry3tdNQYj-e31DnDFQQ@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
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, David Howells <dhowells@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
keyrings@vger.kernel.org, linux-ima-devel@lists.sourceforge.net,
Pavel Shilovsky <pshilov@microsoft.com>,
Alasdair Kergon <agk@redhat.com>,
linux-cifs@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-ima-user@lists.sourceforge.net,
Eric Biggers <ebiggers3@gmail.com>,
linux-raid@vger.kernel.org, linux-fscrypt@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Ofir Drang <ofir.drang@arm.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
samba-technical@lists.samba.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Steve French <sfrench@samba.org>linux-
Subject: Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date: Sat, 10 Jun 2017 17:01:31 +0800 [thread overview]
Message-ID: <20170610090131.GA15594@gondor.apana.org.au> (raw)
In-Reply-To: <CAOtvUMeRtcVcp8HE9oJAkJO35yF9XBsry3tdNQYj-e31DnDFQQ@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
David Howells <dhowells@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Shaohua Li <shli@kernel.org>, Steve French <sfrench@samba.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Eric Biggers <ebiggers3@gmail.com>,
Ofir Drang <ofir.drang@arm.com>,
Pavel Shilovsky <pshilov@microsoft.com>,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
keyrings@vger.kernel.org, linux-raid@vger.kernel.org,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-fscrypt@vger.kernel.org,
linux-ima-devel@lists.sourceforge.net,
linux-ima-user@lists.sourceforge.net,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date: Sat, 10 Jun 2017 17:01:31 +0800 [thread overview]
Message-ID: <20170610090131.GA15594@gondor.apana.org.au> (raw)
In-Reply-To: <CAOtvUMeRtcVcp8HE9oJAkJO35yF9XBsry3tdNQYj-e31DnDFQQ@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
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, David Howells <dhowells@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
keyrings@vger.kernel.org, linux-ima-devel@lists.sourceforge.net,
Pavel Shilovsky <pshilov@microsoft.com>,
Alasdair Kergon <agk@redhat.com>,
linux-cifs@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-ima-user@lists.sourceforge.net,
Eric Biggers <ebiggers3@gmail.com>,
linux-raid@vger.kernel.org, linux-fscrypt@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Ofir Drang <ofir.drang@arm.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
samba-technical@lists.samba.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Steve French <sfrench@samba.org>linux-
Subject: Re: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date: Sat, 10 Jun 2017 09:01:31 +0000 [thread overview]
Message-ID: <20170610090131.GA15594@gondor.apana.org.au> (raw)
In-Reply-To: <CAOtvUMeRtcVcp8HE9oJAkJO35yF9XBsry3tdNQYj-e31DnDFQQ@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: herbert@gondor.apana.org.au (Herbert Xu)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2 01/11] crypto: introduce crypto wait for async op
Date: Sat, 10 Jun 2017 17:01:31 +0800 [thread overview]
Message-ID: <20170610090131.GA15594@gondor.apana.org.au> (raw)
In-Reply-To: <CAOtvUMeRtcVcp8HE9oJAkJO35yF9XBsry3tdNQYj-e31DnDFQQ@mail.gmail.com>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-10 9:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 8:22 [PATCH v2 00/11] introduce crypto wait for async op Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 01/11] crypto: " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-06-10 3:43 ` Herbert Xu
2017-06-10 3:43 ` Herbert Xu
2017-06-10 3:43 ` Herbert Xu
2017-06-10 3:43 ` Herbert Xu
2017-06-10 8:05 ` Gilad Ben-Yossef
2017-06-10 8:05 ` Gilad Ben-Yossef
2017-06-10 8:05 ` Gilad Ben-Yossef
2017-06-10 8:05 ` Gilad Ben-Yossef
2017-06-10 8:05 ` Gilad Ben-Yossef
2017-06-10 9:01 ` Herbert Xu [this message]
2017-06-10 9:01 ` Herbert Xu
2017-06-10 9:01 ` Herbert Xu
2017-06-10 9:01 ` Herbert Xu
2017-06-10 9:01 ` Herbert Xu
2017-05-29 8:22 ` [PATCH v2 02/11] crypto: move algif to generic async completion Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 03/11] crypto: move pub key " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 04/11] crypto: move drbg " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 9:04 ` Stephan Müller
2017-05-29 9:04 ` Stephan Müller
2017-05-29 9:04 ` Stephan Müller
2017-05-29 8:22 ` [PATCH v2 05/11] crypto: move gcm " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 06/11] crypto: move testmgr " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 07/11] dm: move dm-verity " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 08/11] fscrypt: move " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 09/11] cifs: " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 10/11] ima: " Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` [PATCH v2 11/11] crypto: adapt api sample to use async. op wait Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
2017-05-29 8:22 ` Gilad Ben-Yossef
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=20170610090131.GA15594@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=agk@redhat.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiggers3@gmail.com \
--cc=gilad@benyossef.com \
--cc=jaegeuk@kernel.org \
--cc=james.l.morris@oracle.com \
--cc=keyrings@vger.kernel.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-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ofir.drang@arm.com \
--cc=pshilov@microsoft.com \
--cc=samba-technical@lists.samba.org \
--cc=serge@hallyn.com \
--cc=sfrench@samba.org \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.