From: "George Spelvin" <linux@horizon.com>
To: herbert@gondor.apana.org.au, JBeulich@suse.com,
linux@horizon.com, tim.c.chen@linux.intel.com
Cc: linux-kernel@vger.kernel.org, sandyw@twitter.com
Subject: Re: [RFC PATCH] crypto: crc32c-pclmul - Use pmovzxdq to shrink K_table
Date: 28 May 2014 11:32:49 -0400 [thread overview]
Message-ID: <20140528153249.18014.qmail@ns.horizon.com> (raw)
In-Reply-To: <20140528144000.28686.qmail@ns.horizon.com>
Um, yeah, I just noticed the problem with that patch: half of the numbers
in that table are 33 bits, and cause a pile of warnings (not errors,
unfortunately!) from gas that scrolled by when I wasn't looking.
Logically, there should be no need for 33-bit values; they should all be
reducible modulo the polynomial. But that is going to take a slightly
larger change.
next prev parent reply other threads:[~2014-05-28 15:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 14:40 George Spelvin
2014-05-28 15:32 ` George Spelvin [this message]
2014-05-28 22:15 ` [PATCH v2] crypto: crc32c-pclmul - Shrink K_table to 32-bit words George Spelvin
2014-05-28 23:02 ` Tim Chen
2014-05-28 23:55 ` George Spelvin
2014-05-29 3:26 ` George Spelvin
2014-05-29 16:33 ` Tim Chen
2014-05-28 20:47 ` [RFC PATCH] crypto: crc32c-pclmul - Use pmovzxdq to shrink K_table Jan Beulich
2014-05-28 21:47 ` George Spelvin
2014-05-29 6:44 ` Jan Beulich
2014-05-28 22:32 ` Tim Chen
2014-05-28 23:01 ` George Spelvin
2014-05-28 23:28 ` Tim Chen
2014-05-29 23:54 ` George Spelvin
2014-05-30 1:07 ` Tim Chen
2014-05-30 1:16 ` Dave Jones
2014-05-30 17:56 ` Tim Chen
2014-05-30 18:45 ` Dirk Brandewie
2014-05-30 19:32 ` Tim Chen
2014-05-30 19:38 ` Dirk Brandewie
2014-05-30 20:07 ` Tim Chen
2014-05-30 20:15 ` Dirk Brandewie
2014-05-30 1:37 ` George Spelvin
2014-05-30 5:25 ` George Spelvin
2014-05-30 16:10 ` Tim Chen
2014-05-30 16:52 ` George Spelvin
2014-05-30 17:01 ` Tim Chen
2014-06-07 3:08 ` [PATCH v3] crypto: crc32c-pclmul - Shrink K_table to 32-bit words George Spelvin
2014-06-20 18: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=20140528153249.18014.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=JBeulich@suse.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyw@twitter.com \
--cc=tim.c.chen@linux.intel.com \
/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
Powered by JetHome