From: Tejun Heo <htejun@gmail.com>
To: "Huang, Shane" <Shane.Huang@amd.com>
Cc: Holger Hasselmann <hhasselm@web.de>, linux-ide@vger.kernel.org
Subject: Re: Gigabyte GA-MA69VM-S2 can't do 64bit DMA
Date: Fri, 18 Sep 2009 17:09:19 +0900 [thread overview]
Message-ID: <4AB3402F.5010609@gmail.com> (raw)
In-Reply-To: <C8E4BD7D001E44499280E0884BD9DB30010861B7@sshaexmb1.amd.com>
Huang, Shane wrote:
> Hi Tejun,
>
>> -----Original Message-----
>> From: Tejun Heo [mailto:htejun@gmail.com]
>>> ahci 0000:00:12.0: version 3.0_
>>> ahci 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
>>> ahci 0000:00:12.0: Fujitsu-Siemens AMILO Pa 2510: this
>> board can't do 64bit
>>> DMA, forcing 32bit
>>> ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
>>> ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps
>> 0xf impl SATA mode
>>> ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part
>>> It's correct now.
>> Cool, patch posted with the id string shortened.
>
> Just some small questions about this topic:
>
> What is the actual impact of 64-bit DMA not being available?
If IO happens to memory above 4G it will either be bounced (ie. DMA
will be performed to a bounce buffer < 4G which is copied from / to
the original buffer or more likely iommu will kick in.
> How important is it to have this enabled?
>
> In other words, will the performance be improved significantly
> after it is enabled? Do you have any experimental data for it? :-)
There probably won't be any noticeable performance regression if iommu
is working properly and no, I don't have any concrete numbers.
Thanks..
--
tejun
prev parent reply other threads:[~2009-09-18 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 17:50 Gigabyte GA-MA69VM-S2 can't do 64bit DMA Holger Hasselmann
2009-09-15 19:09 ` Tejun Heo
2009-09-16 9:19 ` Holger Hasselmann
2009-09-16 10:49 ` Tejun Heo
2009-09-17 22:12 ` Holger Hasselmann
2009-09-18 0:43 ` Tejun Heo
2009-09-18 1:17 ` Huang, Shane
2009-09-18 8:09 ` Tejun Heo [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=4AB3402F.5010609@gmail.com \
--to=htejun@gmail.com \
--cc=Shane.Huang@amd.com \
--cc=hhasselm@web.de \
--cc=linux-ide@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).