[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <7BD0DE04-7D80-4C0B-AF59-3588762A0EFC@oracle.com>
Date: Thu, 12 Nov 2020 16:09:32 -0500
From: Chuck Lever <chuck.lever@...cle.com>
To: Bruce Fields <bfields@...ldses.org>
Cc: David Howells <dhowells@...hat.com>,
CIFS <linux-cifs@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Trond Myklebust <trond.myklebust@...merspace.com>,
linux-crypto@...r.kernel.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-afs@...ts.infradead.org
Subject: Re: [RFC][PATCH 00/18] crypto: Add generic Kerberos library
> On Nov 12, 2020, at 4:07 PM, Bruce Fields <bfields@...ldses.org> wrote:
>
> On Thu, Nov 12, 2020 at 04:54:06PM +0000, David Howells wrote:
>> Chuck Lever <chuck.lever@...cle.com> wrote:
>>
>>> Really? My understanding of the Linux kernel SUNRPC implementation is
>>> that it uses asynchronous, even for small data items. Maybe I'm using
>>> the terminology incorrectly.
>>
>> Seems to be synchronous, at least in its use of skcipher:
>
> Yes, it's all synchronous. The only cases where we defer and revisit a
> request is when we need to do upcalls to userspace.
>
> (And those upcalls mostly come after we're done with unwrapping and
> verifying a request, so now I'm sort of curious exactly what Chuck was
> seeing.)
I vaguely recall that setting CRYPTO_TFM_REQ_MAY_SLEEP allows the
crypto API to sleep and defer completion.
--
Chuck Lever
Powered by blists - more mailing lists