From: Theodore Ts'o <tytso@mit.edu>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, ecryptfs@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Steffen Klassert <steffen.klassert@secunet.com>,
mhalcrow@google.com
Subject: Re: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
Date: Tue, 19 May 2015 10:39:04 -0400 [thread overview]
Message-ID: <20150519143904.GA25684@thunk.org> (raw)
In-Reply-To: <20150519142755.GB32663@gondor.apana.org.au>
On Tue, May 19, 2015 at 10:27:55PM +0800, Herbert Xu wrote:
> On Tue, May 19, 2015 at 10:14:30AM -0400, Theodore Ts'o wrote:
> >
> > There can be multiple reads going on in parallel, so we're currently
> > creating tfm's as necessary. In fact one of the things that we've
>
> A single tfm is fully-reentrant (as long as you don't change the
> key). So multiple reads/writes on a single file can all use one
> tfm with no locking at all.
Cool, we didn't realize this was the case. Excellent, this makes life
much simpler for us! :-)
Thanks,
- Ted
next prev parent reply other threads:[~2015-05-19 14:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 5:46 [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm Jaegeuk Kim
2015-05-19 5:49 ` Herbert Xu
2015-05-19 6:24 ` Jaegeuk Kim
2015-05-19 6:31 ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim
2015-05-19 6:32 ` Herbert Xu
2015-05-19 6:32 ` [PATCH] " Herbert Xu
2015-05-19 6:58 ` Jaegeuk Kim
2015-05-19 6:59 ` Herbert Xu
2015-05-19 7:13 ` Jaegeuk Kim
2015-05-19 7:15 ` Herbert Xu
2015-05-19 7:27 ` Jaegeuk Kim
2015-05-19 7:30 ` Herbert Xu
2015-05-19 7:59 ` Jaegeuk Kim
2015-05-19 14:14 ` Theodore Ts'o
2015-05-19 14:27 ` Herbert Xu
2015-05-19 14:39 ` Theodore Ts'o [this message]
2015-05-20 7:21 ` Steffen Klassert
2015-05-20 14:59 ` Theodore Ts'o
2015-05-20 15:30 ` Ard Biesheuvel
2015-05-20 15:42 ` 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=20150519143904.GA25684@thunk.org \
--to=tytso@mit.edu \
--cc=davem@davemloft.net \
--cc=ecryptfs@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jaegeuk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).