From: Christoph Lameter <clameter@sgi.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: David Chinner <dgc@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Nathan Scott <nscott@aconex.com>,
Andrea Arcangeli <andrea@suse.de>,
Nick Piggin <nickpiggin@yahoo.com.au>, Mel Gorman <mel@skynet.ie>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
William Lee Irwin III <wli@holomorphy.com>,
Jens Axboe <jens.axboe@oracle.com>,
Badari Pulavarty <pbadari@gmail.com>,
Maxim Levitsky <maximlevitsky@gmail.com>,
Fengguang Wu <fengguang.wu@gmail.com>,
swin wang <wangswin@gmail.com>,
totty.lu@gmail.com, hugh@veritas.com, joern@lazybastard.org
Subject: Re: More Large blocksize benchmarks
Date: Mon, 15 Oct 2007 17:44:08 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710151741200.19172@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071016002231.GA21378@think.oraclecorp.com>
On Mon, 15 Oct 2007, Chris Mason wrote:
> Dave reported that XFS saw much higher write throughput with large
> blocksizes, but so far I'm seeing the most benefits during reads.
Dave's tests were done with an early large blocksize patchset that had
issues with readahead. More recent versions have the fixes by Fengguang
that address the issue.
next prev parent reply other threads:[~2007-10-16 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 0:22 More Large blocksize benchmarks Chris Mason
2007-10-16 0:44 ` Christoph Lameter [this message]
2007-10-16 2:36 ` David Chinner
2007-10-16 13:01 ` Chris Mason
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=Pine.LNX.4.64.0710151741200.19172@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=andrea@suse.de \
--cc=chris.mason@oracle.com \
--cc=dgc@sgi.com \
--cc=fengguang.wu@gmail.com \
--cc=hch@lst.de \
--cc=hugh@veritas.com \
--cc=jens.axboe@oracle.com \
--cc=joern@lazybastard.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=mel@skynet.ie \
--cc=nickpiggin@yahoo.com.au \
--cc=nscott@aconex.com \
--cc=pbadari@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=totty.lu@gmail.com \
--cc=wangswin@gmail.com \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).