From: Christoph Hellwig <hch@infradead.org>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: Josef Bacik <josef@redhat.com>,
hch@infradead.org, 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: Fri, 6 Aug 2010 08:03:58 -0400 [thread overview]
Message-ID: <20100806120358.GA31601@infradead.org> (raw)
In-Reply-To: <4C5BE8DB.5030503@linux.vnet.ibm.com>
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.
next parent reply other threads:[~2010-08-06 12:03 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 ` Christoph Hellwig [this message]
2010-08-07 7:31 ` PATCH 3/6 - direct-io: do not merge logically non-contiguous requests Christian Ehrhardt
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=20100806120358.GA31601@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ehrhardt@linux.vnet.ibm.com \
--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).