Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Harsh Jain <harshjain.prof@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Why null skcipher to copy AAD data?
Date: Tue, 5 Jul 2016 13:03:56 +0800	[thread overview]
Message-ID: <20160705050355.GA5724@gondor.apana.org.au> (raw)
In-Reply-To: <CAFXBA==GZRefGrLxjYtNbViPEyasdvbbHwJ4hS+swtVfSR=HQA@mail.gmail.com>

Harsh Jain <harshjain.prof@gmail.com> wrote:
> 
> Why we need null skcipher to copy AAD from src to dst buffer. We can
> do the same with some function,who can copy data from src sg list to
> dst sg list.

Well first of all we don't have such a function, and even if
you took the trouble of actually writing one would it really
be that much faster than using the null skcipher?

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2016-07-05  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 12:20 Why null skcipher to copy AAD data? Harsh Jain
2016-07-05  5:03 ` Herbert Xu [this message]

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=20160705050355.GA5724@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=harshjain.prof@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox