From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [BLOCK] phys_contig implies hw_contig
Date: Sat, 1 Nov 2003 20:45:47 -0800 [thread overview]
Message-ID: <20031101204547.1c861c42.davem@redhat.com> (raw)
In-Reply-To: <20031101023127.GA14438@gondor.apana.org.au>
On Sat, 1 Nov 2003 13:31:27 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> In ll_merge_requests_fn, it is checking blk_hw_contig_segments even if
> blk_phys_contig_segments succeeds. This means that it may cause two
> physically contiguous segments to be separated because the hw check
> fails.
Your analysis assumes that phys contig implies hw contig, I
believe it does not. There may be limitations in the VMERGE
mechanism a platform implements that causes this situation to
arise.
next prev parent reply other threads:[~2003-11-02 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 2:31 Herbert Xu
2003-11-02 4:45 ` David S. Miller [this message]
2003-11-02 4:47 ` Herbert Xu
2003-11-02 22:10 ` Herbert Xu
2003-11-03 22:40 ` David S. Miller
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=20031101204547.1c861c42.davem@redhat.com \
--to=davem@redhat.com \
--cc=axboe@suse.de \
--cc=herbert@gondor.apana.org.au \
--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
all inboxes | Powered by JetHome®