linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu (Theodore Ts'o)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] crypto: allow to assign gfp_t for __crypto_alloc_tfm
Date: Wed, 20 May 2015 10:59:01 -0400	[thread overview]
Message-ID: <20150520145901.GI2871@thunk.org> (raw)
In-Reply-To: <20150520072118.GN8928@secunet.com>

On Wed, May 20, 2015 at 09:21:20AM +0200, Steffen Klassert wrote:
> The current pcrypt version is used just for IPsec because it supports
> only AEAD type algorithms and does not support request backlog. But
> I have patches to support ablkcipher algorithms and request backlog.
> I could provide them if there is interest in it.

I don't know the crypto layer well enough, and I certainly don't know
how to deal with things like ARM CPU's with "big-little" architectures
to understand what we might need to do to power optimize things for
mobile handsets.  But if someone has time to look at this, that would
be great.

					- Ted

  reply	other threads:[~2015-05-20 14:59 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
2015-05-20  7:21                   ` Steffen Klassert
2015-05-20 14:59                     ` Theodore Ts'o [this message]
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=20150520145901.GI2871@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).