From: Tim Chen <tim.c.chen@linux.intel.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"David S. Miller" <davem@davemloft.net>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Chaohong Guo <chaohong.guo@intel.com>,
Austin Zhang <austin_zhang@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org,
James Guilford <james.guilford@intel.com>,
Wajdi Feghali <wajdi.k.feghali@intel.com>,
Min Li <min.a.li@intel.com>, David Cote <david.m.cote@intel.com>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH 2/3 v2] Optimize CRC32C calculation with PCLMULQDQ instruction
Date: Tue, 26 Feb 2013 08:57:41 -0800 [thread overview]
Message-ID: <1361897861.17632.222.camel@schen9-DESK> (raw)
In-Reply-To: <20130226095424.GA19924@gondor.apana.org.au>
On Tue, 2013-02-26 at 17:54 +0800, Herbert Xu wrote:
> On Thu, Sep 27, 2012 at 03:44:22PM -0700, Tim Chen wrote:
> > This patch adds the crc_pcl function that calculates CRC32C checksum using the
> > PCLMULQDQ instruction on processors that support this feature. This will
> > provide speedup over using CRC32 instruction only.
> > The usage of PCLMULQDQ necessitate the invocation of kernel_fpu_begin and
> > kernel_fpu_end and incur some overhead. So the new crc_pcl function is only
> > invoked for buffer size of 512 bytes or more. Larger sized
> > buffers will expect to see greater speedup. This feature is best used coupled
> > with eager_fpu which reduces the kernel_fpu_begin/end overhead. For
> > buffer size of 1K the speedup is around 1.6x and for buffer size greater than
> > 4K, the speedup is around 3x compared to original implementation in crc32c-intel
> > module. Test was performed on Sandy Bridge based platform with constant frequency
> > set for cpu.
> >
> > A white paper detailing the algorithm can be found here:
> > http://download.intel.com/design/intarch/papers/323405.pdf
> >
> > Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
Acked.
BTW, Herbert, I've also sent you a patch a few days ago to update the
link to the whitepaper on the CRC32C algorithm in the code. Wonder if
you have received it. Thanks.
Tim
next prev parent reply other threads:[~2013-02-26 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1348784343.git.tim.c.chen@linux.intel.com>
2012-09-27 22:44 ` [PATCH 0/3 v2] Optimize CRC32C calculation using PCLMULQDQ in crc32c-intel module Tim Chen
2012-09-28 2:54 ` H. Peter Anvin
[not found] ` <CAA-+O6EkeJQtO=GFhDCZxFoX9L42CAJW71oT2miivOKL9MzDyA@mail.gmail.com>
2012-10-05 16:47 ` Tim Chen
2012-10-15 14:31 ` Herbert Xu
2012-09-27 22:44 ` [PATCH 1/3 v2] Rename crc32c-intel.c to crc32c-intel_glue.c Tim Chen
2012-09-27 22:44 ` [PATCH 2/3 v2] Optimize CRC32C calculation with PCLMULQDQ instruction Tim Chen
2013-02-26 9:54 ` Herbert Xu
2013-02-26 16:57 ` Tim Chen [this message]
2013-02-27 2:02 ` Herbert Xu
2012-09-27 22:44 ` [PATCH 3/3 v2] Added speed test in tcrypt for crc32c Tim Chen
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=1361897861.17632.222.camel@schen9-DESK \
--to=tim.c.chen@linux.intel.com \
--cc=austin_zhang@linux.intel.com \
--cc=chaohong.guo@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.cote@intel.com \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.hengli.com.au \
--cc=hpa@zytor.com \
--cc=james.guilford@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.a.li@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=wajdi.k.feghali@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
all inboxes | Powered by JetHome®