From: Matthew Wilcox <matthew@wil.cx>
To: Szabolcs Szakacsits <szaka@ntfs-3g.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: XFS vs Elevators (was Re: [PATCH RFC] nilfs2: continuous snapshotting file system)
Date: Thu, 21 Aug 2008 05:53:10 -0600 [thread overview]
Message-ID: <20080821115310.GP8318@parisc-linux.org> (raw)
In-Reply-To: <20080821060418.GC5706@disturbed>
On Thu, Aug 21, 2008 at 04:04:18PM +1000, Dave Chinner wrote:
> One thing I just found out - my old *laptop* is 4-5x faster than the
> 10krpm scsi disk behind an old cciss raid controller. I'm wondering
> if the long delays in dispatch is caused by an interaction with CTQ
> but I can't change it on the cciss raid controllers. Are you using
> ctq/ncq on your machine? If so, can you reduce the depth to
> something less than 4 and see what difference that makes?
I don't think that's going to make a difference when using CFQ. I did
some tests that showed that CFQ would never issue more than one IO at a
time to a drive. This was using sixteen userspace threads, each doing a
4k direct I/O to the same location. When using noop, I would get 70k
IOPS and when using CFQ I'd get around 40k IOPS.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-08-21 11:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080820004326.519405a2.akpm@linux-foundation.org>
[not found] ` <200808201613.AA00212@capsicum.lab.ntt.co.jp>
[not found] ` <Pine.LNX.4.61.0808202352450.4532@dhcppc2>
[not found] ` <20080820143916.1a7eddab.akpm@linux-foundation.org>
[not found] ` <20080821021259.GA5706@disturbed>
[not found] ` <Pine.LNX.4.62.0808210535450.25448@tamago.serverit.net>
2008-08-21 5:15 ` XFS vs Elevators (was Re: [PATCH RFC] nilfs2: continuous snapshotting file system) Dave Chinner
2008-08-21 6:00 ` gus3
2008-08-21 6:14 ` Dave Chinner
[not found] ` <200808211700.39584.nickpiggin@yahoo.com.au>
2008-08-21 8:53 ` Dave Chinner
2008-08-21 14:52 ` Chris Mason
[not found] ` <200808211933.34565.nickpiggin@yahoo.com.au>
2008-08-21 17:08 ` Dave Chinner
[not found] ` <200808221229.11069.nickpiggin@yahoo.com.au>
2008-08-25 1:59 ` Dave Chinner
2008-08-25 12:01 ` Jamie Lokier
2008-08-26 3:07 ` Dave Chinner
2008-08-26 3:50 ` david
2008-08-27 1:20 ` Dave Chinner
2008-08-27 21:54 ` david
2008-08-28 1:08 ` Dave Chinner
2008-08-21 6:04 ` Dave Chinner
2008-08-21 8:07 ` Aaron Carroll
2008-08-21 8:25 ` Dave Chinner
2008-08-21 11:02 ` Martin Steigerwald
2008-08-21 15:00 ` Martin Steigerwald
2008-08-21 17:10 ` Szabolcs Szakacsits
2008-08-21 17:33 ` Szabolcs Szakacsits
2008-08-22 2:24 ` Dave Chinner
2008-08-22 6:49 ` Martin Steigerwald
2008-08-22 12:44 ` Szabolcs Szakacsits
2008-08-23 12:52 ` Szabolcs Szakacsits
2008-08-21 11:53 ` Matthew Wilcox [this message]
2008-08-21 15:56 ` Dave Chinner
2008-08-21 11:05 Martin Knoblauch
2008-08-21 15:59 ` Dave Chinner
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=20080821115310.GP8318@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szaka@ntfs-3g.org \
--cc=xfs@oss.sgi.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