From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josef Bacik <josef@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: PATCH 3/6 - direct-io: do not merge logically non-contiguous requests
Date: Sat, 07 Aug 2010 09:31:14 +0200 [thread overview]
Message-ID: <4C5D0BC2.1040706@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100806120358.GA31601@infradead.org>
On 08/06/2010 02:03 PM, Christoph Hellwig wrote:
> Something is deeply wrong here. Raw block device access has a 1:1
> mapping between logical and physical block numbers. They really should
> never be non-contiguous.
At least I did nothing I know about to break it :-)
As I mentioned just iozone using direct I/O (-I flag of iozone then
using O_DIRECT for the file) on a ext2 file-system.
The file system was coming clean out of mkfs the file was written with
iozone one step before the traced read run.
The only uncommon thing here might be the block device, which is a scsi
disk on our SAN servers (I'm running on s390) - so the driver in charge
is zfcp (drivers/s390/scsi/).
I could use dasd (drivers/s390/block) disks as well, but I have no
blktrace of them yet - what I already know is that they show a similar
cost increase. On monday I should be able to get machine resources to
verify that both disk types are affected.
Let me know if I can do anything else on my system to shed some light on
the matter.
--
Grüsse / regards, Christian Ehrhardt
IBM Linux Technology Center, System z Linux Performance
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-07 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C5BE8DB.5030503@linux.vnet.ibm.com>
2010-08-06 12:03 ` PATCH 3/6 - direct-io: do not merge logically non-contiguous requests Christoph Hellwig
2010-08-07 7:31 ` Christian Ehrhardt [this message]
2010-08-10 18:40 ` Jeff Moyer
2010-08-11 1:55 ` Josef Bacik
2010-08-11 13:27 ` Jeff Moyer
2010-08-11 14:08 ` Josef Bacik
2010-08-06 10:50 Christian Ehrhardt
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=4C5D0BC2.1040706@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).