From: Andi Kleen <ak@suse.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: X86_64 + VIA + 4g problems
Date: Mon, 2 Jan 2006 20:53:31 +0100 [thread overview]
Message-ID: <200601022053.31534.ak@suse.de> (raw)
In-Reply-To: <43B97C6D.7010902@shaw.ca>
On Monday 02 January 2006 20:18, Robert Hancock wrote:
> Andi Kleen wrote:
> > When you not compile in the SKGE network driver does everything else work?
> > skge supports 64bit DMA, so it shouldn't use any IOMMU.
>
> Are you sure this is skge?
I grepped for the output in that badly truncated logfile and skge hit.
> Anyway, even if the driver does support
> 64-bit DMA, I would be surprised if a desktop motherboard had the
> Ethernet chip connected via a 64-bit PCI bus.
I meant 64bit DMA, aka double address cycle, not a 64bit wide PCI-X bus.
That works on a 32bit PCI bus too. On modern boards it's likely PCI
Express anyways for on board devices.
>
> This brings up something I've been wondering. It's possible to run most
> 64-bit capable PCI devices in a 32-bit slot (i.e. with the 64-bit part
> hanging out of the slot). In this configuration the device will not be
> able to use 64-bit DMA (unless it supports dual address cycle). However,
> who is supposed to detect this and know to not try to use DMA addresses
> above 4GB on that device?
64bit PCI-X bus has nothing to do with the addressing capability. It
just gives you more bandwidth.
-Andi
next prev parent reply other threads:[~2006-01-02 19:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5qvTv-8f-17@gated-at.bofh.it>
[not found] ` <5qAKf-7n4-19@gated-at.bofh.it>
2006-01-02 19:18 ` X86_64 + VIA + 4g problems Robert Hancock
2006-01-02 19:53 ` Andi Kleen [this message]
2006-01-02 20:15 ` Robert Hancock
2006-01-02 20:39 ` Andi Kleen
[not found] ` <5qBcJ-7ZZ-5@gated-at.bofh.it>
[not found] ` <5qDez-2Qf-19@gated-at.bofh.it>
[not found] ` <5r2nz-63n-233@gated-at.bofh.it>
2006-01-04 3:03 ` Robert Hancock
2006-01-02 11:09 Dieter Stüken
2006-01-02 12:26 ` Carsten Otto
2006-01-02 16:22 ` Andi Kleen
2006-01-02 16:52 ` Carsten Otto
2006-01-02 17:46 ` Carsten Otto
2006-01-02 19:01 ` Andi Kleen
2006-01-03 22:54 ` Carsten Otto
2006-01-03 10:04 ` Dieter Stüken
2006-01-03 13:58 ` Andi Kleen
2006-01-03 19:56 ` Dieter Stüken
2006-01-03 21:08 ` Dieter Stüken
2006-01-03 21:26 ` Andi Kleen
2006-01-04 10:27 ` Dieter Stüken
2006-01-04 10:57 ` Andi Kleen
2006-01-04 10:57 ` Dieter Stüken
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=200601022053.31534.ak@suse.de \
--to=ak@suse.de \
--cc=hancockr@shaw.ca \
--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