Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: Questions about the Crypto API
Date: Fri, 9 Aug 2013 09:55:14 -0300	[thread overview]
Message-ID: <20130809125513.GA7674@oc8526070481.ibm.com> (raw)
In-Reply-To: <065BBB7616BCE543832A2EF096986B940A05ADCD@039-SN2MPN1-011.039d.mgd.msft.net>

On Thu, Aug 08, 2013 at 02:50:41PM +0000, Garg Vakul-B16394 wrote:
> Hi Herbert
> 
> 
> > -----Original Message-----
> > From: linux-crypto-owner@vger.kernel.org [mailto:linux-crypto-
> > owner@vger.kernel.org] On Behalf Of Herbert Xu
> > Sent: Tuesday, August 06, 2013 12:30 PM
> > To: Marcelo Cerri
> > Cc: linux-crypto@vger.kernel.org
> > Subject: Re: Questions about the Crypto API
> > 
> > On Mon, Aug 05, 2013 at 05:25:57PM -0300, Marcelo Cerri wrote:
> > >
> > > My first doubt is regarding which kind of concurrency the Crypto API
> > > allows. For example, can a single `struct crypto_tfm` be used by two
> > > concurrent calls? I'm asking about that because I noticed that for
> > 
> > Yes.
> > 
> 
> In this post, you mentioned that tfm is single threaded.
> Am I misinterpreting your statement?
> 
> http://www.mail-archive.com/linux-crypto@vger.kernel.org/msg08689.html
> 

Hi Herbert,

I also would like to better understand that. It doesn't seem natural for
me that a single tfm can be used by multiple kernel threads.

Best regards,
Marcelo

  reply	other threads:[~2013-08-09 12:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 20:25 Questions about the Crypto API Marcelo Cerri
2013-08-06  7:00 ` Herbert Xu
2013-08-06 12:05   ` Marcelo Cerri
2013-08-06 14:16     ` Marcelo Cerri
2013-08-08  5:01       ` Herbert Xu
2013-08-08 14:04         ` Hsieh, Che-Min
2013-08-10  1:21           ` Herbert Xu
2013-08-10  2:15             ` Hsieh, Che-Min
2013-08-10  6:17               ` Herbert Xu
2013-08-08  5:02     ` Herbert Xu
2013-08-08 14:50   ` Garg Vakul-B16394
2013-08-09 12:55     ` Marcelo Cerri [this message]
     [not found]       ` <A83C99F8370D4D42BEB2D2B3153A6BBC23D55A6E@NASANEXD02C.na.qualcomm.com>
2013-08-10  1:15         ` Herbert Xu
2013-08-12 13:49           ` Marcelo Cerri
2013-08-13 19:25             ` Hsieh, Che-Min
2013-08-16  6:37               ` Herbert Xu
2013-08-16  6:30             ` 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=20130809125513.GA7674@oc8526070481.ibm.com \
    --to=mhcerri@linux.vnet.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /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