On Wed, 2013-04-17 at 20:58 +0300, Jussi Kivilinna wrote:
> On 16.04.2013 19:20, Tim Chen wrote:
> > These are simple tests to do sanity check of CRC T10 DIF hash. The
> > correctness of the transform can be checked with the command
> > modprobe tcrypt mode=47
> > The speed of the transform can be evaluated with the command
> > modprobe tcrypt mode=320
> >
> > Set the cpu frequency to constant and turn turbo off when running the
> > speed test so the frequency governor will not tweak the frequency and
> > affects the measurements.
> >
> > Signed-off-by: Tim Chen <tim.c.chen@xxxxxxxxxxxxxxx>
> > Tested-by: Keith Busch <keith.busch@xxxxxxxxx>
> <snip>
> >
> > +#define CRCT10DIF_TEST_VECTORS 2
> > +static struct hash_testvec crct10dif_tv_template[] = {
> > + {
> > + .plaintext = "abc",
> > + .psize = 3,
> > +#ifdef __LITTLE_ENDIAN
> > + .digest = "\x3b\x44",
> > +#else
> > + .digest = "\x44\x3b",
> > +#endif
> > + }, {
> > + .plaintext =
> > + "abcddddddddddddddddddddddddddddddddddddddddddddddddddddd",
> > + .psize = 56,
> > +#ifdef __LITTLE_ENDIAN
> > + .digest = "\xe3\x9c",
> > +#else
> > + .digest = "\x9c\xe3",
> > +#endif
> > + .np = 2,
> > + .tap = { 28, 28 }
> > + }
> > +};
> > +
>
> Are these large enough to test all code paths in the PCLMULQDQ implementation?
We have tested the implementation exhaustively for large number of code paths.
The tcrypt tests here are only meant for sanity check, and not for
exhaustive tests.
Tim
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
