From: Steffen Persvold <sp@scali.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] BitKeeper tree for 2.4.x
Date: Fri, 18 Oct 2002 02:32:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805192@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805154@msgid-missing>
On Thu, 17 Oct 2002, Grant Grundler wrote:
> Steffen Persvold wrote:
> > Kinda complicated though... I thought the IO system didn't use coherence
> > protocols, and it was because of that we needed API functions such as
> > pci_dma_sync_single() and pci_dma_sync_sg() to manually ensure coherence..
>
> The original problem was some IOMMU's can not support a static translation
> for all physical memory - ie virt_to_bus() wouldn't work.
> "manual coherence" works because the design accomodates SW IOTLB
> ("bounce buffers") model.
>
> Supported HP PARISC and IA64 IOMMU's participate in the coherency protocol.
>
True, but I still can't see how a PTE with the WC attribute (in the CPU
MMU) can affect the coherency protocol the IOMMU uses on DMA read
transfers. I thought the WC attribute just controlled how the CPU buffered
data.
Anyway, although I agree that the availability of the WC feature should be
checked with the information from the firware, I don't agree that this
should be done now on the 2.4 series. Atleast don't remove WC (or UC)
support in any 2.4 kernels before the validation routines are ready and
implemented.
Regards,
--
Steffen Persvold | Scali AS
mailto:sp@scali.com | http://www.scali.com
Tel: (+47) 2262 8950 | Olaf Helsets vei 6
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY
prev parent reply other threads:[~2002-10-18 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 19:42 [Linux-ia64] BitKeeper tree for 2.4.x Bjorn Helgaas
2002-10-14 17:42 ` Bjorn Helgaas
2002-10-14 18:17 ` Steffen Persvold
2002-10-14 20:44 ` Grant Grundler
2002-10-17 16:46 ` Bjorn Helgaas
2002-10-17 18:16 ` Steffen Persvold
2002-10-17 18:31 ` Steffen Persvold
2002-10-17 19:38 ` Bjorn Helgaas
2002-10-17 21:53 ` Steffen Persvold
2002-10-17 22:10 ` Grant Grundler
2002-10-18 2:32 ` Steffen Persvold [this message]
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=marc-linux-ia64-105590709805192@msgid-missing \
--to=sp@scali.com \
--cc=linux-ia64@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