From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com, davidm@napali.hpl.hp.com
Cc: manfred@colorfullife.com, axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: problem with blk_queue_bounce_limit()
Date: Thu, 05 Jun 2003 23:52:49 -0700 (PDT) [thread overview]
Message-ID: <20030605.235249.35666087.davem@redhat.com> (raw)
In-Reply-To: <16096.14281.621282.67906@napali.hpl.hp.com>
Ok, ide-lib.c can call blk_queue_bounce_limit with only
3 different args:
1) BLK_BOUNCE_HIGH (--> blk_max_pfn)
2) BLK_BOUNCE_ANY (--> blk_max_lo_pfn)
3) pci_dev->dma_mask
David, you're not setting PCI_DMA_BUS_IS_PHYS properly.
For IOMMU it should be set to zero. This tells the block
layer if you're IOMMU or not.
I knew it would be a bug like this.
Anyways, the problem case is #3 above and that will never
happen if you start setting PCI_DMA_BUS_IS_PHYS to zero
as appropriate.
next prev parent reply other threads:[~2003-06-06 6:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 6:42 problem with blk_queue_bounce_limit() David Mosberger
2003-06-05 7:20 ` David S. Miller
2003-06-06 6:42 ` David Mosberger
2003-06-06 6:45 ` David S. Miller
2003-06-06 6:54 ` David Mosberger
2003-06-06 7:08 ` David S. Miller
2003-06-06 6:52 ` David S. Miller [this message]
2003-06-06 7:19 ` David Mosberger
2003-06-06 7:32 ` David S. Miller
2003-06-06 7:44 ` Christoph Hellwig
2003-06-06 7:43 ` David S. Miller
2003-06-06 7:51 ` Christoph Hellwig
2003-06-06 20:13 ` David Mosberger
2003-06-07 6:44 ` David S. Miller
2003-06-07 7:05 ` David Mosberger
2003-06-07 7:11 ` David S. Miller
2003-06-10 20:01 ` David Mosberger
2003-06-12 6:47 ` David S. Miller
2003-06-15 7:06 ` Anton Blanchard
2003-06-15 7:11 ` David S. Miller
2003-06-15 8:04 ` Anton Blanchard
2003-06-15 8:18 ` David S. Miller
2003-06-07 7:20 ` David Mosberger
2003-06-07 7:19 ` David S. Miller
2003-06-07 9:44 ` Russell King
2003-06-07 9:47 ` David S. Miller
2003-06-07 13:23 ` Christoph Hellwig
2003-06-10 20:24 ` David Mosberger
2003-06-06 18:06 James Bottomley
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=20030605.235249.35666087.davem@redhat.com \
--to=davem@redhat.com \
--cc=axboe@suse.de \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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).