From: Kim Phillips <kim.phillips@freescale.com>
To: jhsiao@amcc.com
Cc: linuxppc-dev@ozlabs.org, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] AMCC Crypto4xx Device Driver v4]
Date: Mon, 8 Dec 2008 18:35:52 -0600 [thread overview]
Message-ID: <20081208183552.744cb4ae.kim.phillips@freescale.com> (raw)
In-Reply-To: <1228773307.4906.14.camel@jhsiao-usb>
On Mon, 08 Dec 2008 13:55:07 -0800
James Hsiao <jhsiao@amcc.com> wrote:
> >> + /* figure how many gd is needed */
> >> + if (aad_len) {
> >> + num_gd = get_sg_count(assoc, aad_len) +
> >> + get_sg_count(src, datalen);
>
> > this is dead code - aad_len is never non-zero - is there some code
> > missing from crypto4xx_alg.c? Also, IIRC, assoc is a superset of src,
> > so I believe something like num_gd = get_sg_count(assoc, aad_len +
> > datalen) would work better - this should also permit removal of the
> > nbytes reached check in [1] in get_sg_count.
>
> For the get num_gd, assoc and src are two different scatter_lists. One
> for the packet and one for the aad, so, it makes more sense to me to
> count them seperately. Yes?
ok I looked it up - they are disjoint sg lists, so, yes, you're right.
> The way to driver pass aad and aad_len is from crypto4xx_build_pd.
> This aad support will be used in the future. Do you want me to remover
> from the current release? The reason I have it in, is to avoid too much
> code change for the future release.
removing it would definitely make both this and any forthcoming aead
patches more on topic and thus easier to review (plus I suspect adding
unused code to the kernel is generally frowned upon...)
Kim
next prev parent reply other threads:[~2008-12-09 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:17 [PATCH] AMCC Crypto4xx Device Driver v4] James Hsiao
2008-12-05 1:32 ` Kim Phillips
2008-12-05 5:41 ` Stefan Roese
2008-12-08 18:12 ` Kim Phillips
2008-12-05 23:24 ` James Hsiao
2008-12-08 18:09 ` Kim Phillips
2008-12-08 21:55 ` James Hsiao
2008-12-09 0:35 ` Kim Phillips [this message]
2008-12-09 0:56 ` James Hsiao
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=20081208183552.744cb4ae.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=herbert@gondor.apana.org.au \
--cc=jhsiao@amcc.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).