From: Chris Mason <chris.mason@oracle.com>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: crc32c implementation on x86 with SSE4.2... CONFIG_BTRFS_HW_SUM
Date: Thu, 16 Oct 2008 09:49:04 -0400 [thread overview]
Message-ID: <1224164944.6938.61.camel@think.oraclecorp.com> (raw)
In-Reply-To: <f058a9c30810160640r3a8c8427hc8b35d6881583fb5@mail.gmail.com>
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.
> Its protected by a ifdef CONFIG_BTRFS_HW_SUM, and if we're executing
> on the right cpu, that will bypass the kernel implementation of
> crc32c.
>
The Btrfs support for intel's faster crc32c came from a patch intel
posted to linux-kernel. I just hacked it up a bit at the time because I
didn't want to wait for mainline to include the work.
I don't see intel's patches in mainline yet, but I know there was a plan
to get them there.
-chris
next prev parent reply other threads:[~2008-10-16 13:49 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 [this message]
2008-10-17 6:37 ` Tomasz Torcz
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=1224164944.6938.61.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.filipe@gmail.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