linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Andi Kleen <andi@firstfloor.org>
Cc: Chris Mason <chris.mason@oracle.com>,
	Freek Dijkstra <Freek.Dijkstra@sara.nl>,
	linux-btrfs@vger.kernel.org
Subject: Re: Poor read performance on high-end server
Date: Sun, 08 Aug 2010 07:04:38 -0400	[thread overview]
Message-ID: <4C5E8F46.5010706@kernel.dk> (raw)
In-Reply-To: <87r5i98tdf.fsf@basil.nowhere.org>

On 08/08/2010 03:18 AM, Andi Kleen wrote:
> Jens Axboe <axboe@kernel.dk> writes:
>>
>> 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.
> 
> I have a patch for that, will post it later: autoloading of modules
> based on x86 cpuinfo.

Great, it is pretty annoying to have to do it manually. Sometimes
you forget. And it's not possible to de-select CRC32C and have
the intel variant loaded.

-- 
Jens Axboe


  reply	other threads:[~2010-08-08 11:04 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
2010-08-08  7:18     ` Andi Kleen
2010-08-08 11:04       ` Jens Axboe [this message]
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=4C5E8F46.5010706@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Freek.Dijkstra@sara.nl \
    --cc=andi@firstfloor.org \
    --cc=chris.mason@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).