All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: linux-crypto@vger.kernel.org
Cc: Dave Hansen <dave@linux.vnet.ibm.com>
Subject: Per-cpu tfm allocation/free functions
Date: Thu, 01 Dec 2011 11:01:00 -0600	[thread overview]
Message-ID: <4ED7B2CC.3090209@linux.vnet.ibm.com> (raw)

linux-crypto,

I am currently working on the zcache RAM compression driver (in the staging 
tree) and have a question.

I am looking to use the crypto compression API instead of the hardcoded LZO
calls that are in there right now, but I need to allocate a tfm per cpu per
compression algorithm being used.

I've already written the code but it looks very similar to what is already in
ipcomp_alloc/free_tfms() in net/xfrm/xfrm_ipcomp.c.

Has there ever been any talk about implementing functions like that inside
the cryptographic API in order to prevent duplicate per-cpu code by the users?

Would there be any interest/objections regarding a patch that did implement them? 

--
Seth

                 reply	other threads:[~2011-12-01 17:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4ED7B2CC.3090209@linux.vnet.ibm.com \
    --to=sjenning@linux.vnet.ibm.com \
    --cc=dave@linux.vnet.ibm.com \
    --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 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.