From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: safemode@comcast.net
Subject: Re: pci-dma disables iommu on nforce4 motherboards?
Date: Sat, 24 Dec 2005 17:37:07 -0600 [thread overview]
Message-ID: <43ADDBA3.9010701@shaw.ca> (raw)
In-Reply-To: <5njvv-JD-11@gated-at.bofh.it>
Ed Sweetman wrote:
> I have an asus A8N-E motherboard and recieve the following message on boot.
> PCI-DMA: Disabling IOMMU.
>
> I have no issues with anything not functioning. I guess i'm just
> curious as to why this is done and if i'm missing out on any sort of
> performance gain by not using the iommu. I have less than 4GB of ram,
> would that be why it's disabled (which is why i think it is)? -
The IOMMU is not needed if your RAM all lies below 4GB (note that due to
memory space used for PCI and PCI-E resources, even with only 4GB of
memory, some may end up above 4GB). The purpose of the IOMMU is to allow
32-bit devices which cannot access memory above 4GB to read from such
memory. If the system does not have an IOMMU (i.e. the Intel CPUs with
EM64T) then bounce buffers must be used when these devices want to
perform DMA to memory above 4GB, which reduces performance.
On some platforms the IOMMU can be used to remap memory such that a
discontigous memory region appears contiguous to the device, so that it
can perform DMA transfers in larger chunks. I suspect the performance
benefit of this is somewhat negated by the time to set up the IOMMU
mapping, however.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-12-24 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5njvv-JD-11@gated-at.bofh.it>
2005-12-24 23:37 ` Robert Hancock [this message]
2005-12-24 15:20 pci-dma disables iommu on nforce4 motherboards? Ed Sweetman
2005-12-24 15:53 ` Jeff Garzik
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=43ADDBA3.9010701@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@comcast.net \
/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