From: Chris Mason <chris.mason@oracle.com>
To: Sander <sander@humilis.net>
Cc: Jens Axboe <axboe@kernel.dk>,
Freek Dijkstra <Freek.Dijkstra@sara.nl>,
linux-btrfs@vger.kernel.org
Subject: Re: Poor read performance on high-end server
Date: Fri, 20 Aug 2010 10:37:35 -0400 [thread overview]
Message-ID: <20100820143735.GE5854@think> (raw)
In-Reply-To: <20100820045344.GB28712@attic.humilis.net>
On Fri, Aug 20, 2010 at 06:53:44AM +0200, Sander wrote:
> Chris Mason wrote (ao):
> > On Fri, Aug 06, 2010 at 01:55:21PM +0200, Jens Axboe wrote:
> > > Also, I didn't see Chris mention this, but if you have a newer intel box
> > > you can use hw accellerated crc32c instead. For some reason my test box
> > > always loads crc32c and not crc32c-intel, so I need to do that manually.
> > > That helps a lot with higher transfer rates. You can check support for
> > > hw crc32c by checking for the 'sse4_2' flag in /proc/cpuinfo.
> >
> > Yeah, the HW assisted crc does make a huge difference.
>
> The above says "newer intel box". I did some googling and it seems to
> mean really Intel CPUs only, not AMD, correct?
>
> Is there a way to get hardware support for crc32c on ARM based systems?
So far I only know of the intel sse4.2 systems that support this.
-chris
next prev parent reply other threads:[~2010-08-20 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 14:05 Poor read performance on high-end server Freek Dijkstra
2010-08-05 14:51 ` Chris Mason
2010-08-05 21:21 ` Freek Dijkstra
2010-08-05 22:13 ` Daniel J Blueman
2010-08-06 11:41 ` Chris Mason
2010-08-06 11:55 ` Jens Axboe
2010-08-06 11:59 ` Chris Mason
2010-08-20 4:53 ` Sander
2010-08-20 14:37 ` Chris Mason [this message]
2010-08-08 7:18 ` Andi Kleen
2010-08-08 11:04 ` Jens Axboe
2010-08-09 14:45 ` Freek Dijkstra
2010-08-10 0:55 ` Chris Mason
2010-08-05 14:54 ` Daniel J Blueman
2010-08-05 16:21 ` Mathieu Chouquet-Stringer
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=20100820143735.GE5854@think \
--to=chris.mason@oracle.com \
--cc=Freek.Dijkstra@sara.nl \
--cc=axboe@kernel.dk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sander@humilis.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.