public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Stüken" <stueken@conterra.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X86_64 + VIA + 4g problems
Date: Wed, 04 Jan 2006 11:27:10 +0100	[thread overview]
Message-ID: <43BBA2FE.5060006@conterra.de> (raw)
In-Reply-To: <p731wzpjtvm.fsf@verdi.suse.de>

Andi Kleen wrote:
> [can you please not always drop me from cc with each reply?] 

sorry, I thought the other way around: it would be annoying
to get each mail twice...

I just found a mailing list "discuss@x86-64.org". Would it be
better to turn over there, instead of polluting linux.kernel
by this?

>> But swiotlb=force works well! 
>
> This means your PCI bridge doesn't support addresses >4GB. 
>
>> The pci-gart.c patch seems to disable dma.
> 
> Only DMA for addresses >4GB.
> 
> If your torture test involves more than 64MB of IO in flight
> you might also need to increase the bounce buffer area
> with swiotlb=128M or somesuch. 

I'm about to understand whats going on. So should I use the
dma patch INSTEAD of "swiotlb=force"? I'll try that tonight.

> When you not compile in the SKGE network driver does everything else work? 

I may test it again, but all seemed to work without any patch or
swiotlb settings when running without the SKGE network driver.

So, how does this work, if my PCI bridge generally fails above 4G?

Problems arise not until I enable/use the network driver.
Does the dma-patch disable DMA for all PCI devices or only
for those which cause problems (like my SKGE)?

Dieter.
-- 
Dieter Stüken, con terra GmbH, Münster
     stueken@conterra.de
     http://www.conterra.de/
     (0)251-7474-501

  parent reply	other threads:[~2006-01-04 10:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02 11:09 X86_64 + VIA + 4g problems 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 [this message]
2006-01-04 10:57         ` Andi Kleen
2006-01-04 10:57       ` Dieter Stüken
     [not found] <5qvTv-8f-17@gated-at.bofh.it>
     [not found] ` <5qAKf-7n4-19@gated-at.bofh.it>
2006-01-02 19:18   ` Robert Hancock
2006-01-02 19:53     ` Andi Kleen
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

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=43BBA2FE.5060006@conterra.de \
    --to=stueken@conterra.de \
    --cc=ak@suse.de \
    --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