From: Tomasz Torcz <tomek@crocom.com.pl>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: crc32c implementation on x86 with SSE4.2... CONFIG_BTRFS_HW_SUM
Date: Fri, 17 Oct 2008 08:37:11 +0200 [thread overview]
Message-ID: <1224225431.3360.16.camel@s1.crocom.com.pl> (raw)
In-Reply-To: <1224164944.6938.61.camel@think.oraclecorp.com>
Dnia 2008-10-16, czw o godzinie 09:49 -0400, Chris Mason pisze:
> On Thu, 2008-10-16 at 14:40 +0100, Miguel Sousa Filipe wrote:
> > Hi there,
> >
> > I noticed that btrfs, in the git tree, has its own implementation of
> > crc32c for x86 with SSE4.2 that implement a crc32 instruction.. it
> > appears.
> I don't see intel's patches in mainline yet, but I know there was a
plan
> to get them there.
It seems to be merged:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8cb51ba8e06570a5fff674b3744d12a1b089f2d0
Using generic, replaceable by arch version is surely better. This way
you can avoid implementing crc32 for each architecture (like, for
example UltraSPARC T2, which computes crc at healthy 48 GB/s).
--
Tomasz Torcz
prev parent reply other threads:[~2008-10-17 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 13:40 crc32c implementation on x86 with SSE4.2... CONFIG_BTRFS_HW_SUM Miguel Sousa Filipe
2008-10-16 13:49 ` Chris Mason
2008-10-17 6:37 ` Tomasz Torcz [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=1224225431.3360.16.camel@s1.crocom.com.pl \
--to=tomek@crocom.com.pl \
--cc=linux-btrfs@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