public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "=?iso-8859-1?q?Dieter_St=FCken?= <stueken"@conterra.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: X86_64 + VIA + 4g problems
Date: 03 Jan 2006 22:26:06 +0100	[thread overview]
Message-ID: <p737j9hype9.fsf@verdi.suse.de> (raw)
In-Reply-To: <43BAE7E3.6070504@conterra.de>

Dieter Stüken <stueken@conterra.de> writes:
[can you please not always drop me from cc with each reply?]

Dieter Stüken <stueken@conterra.de> writes:

> OK, here are my last results for today:
>
> using "iommu=allowed" did not work. System freezes during initialization
> of the PDC20318, which is on the external PCI bus.
>
> 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.

> Is this the DMA my PCI devices
> perform them self? As I learned, they may perform DMA even above 4g if all
> works well. Thus I may be happy without any IOMMU. As I saw my system working
> even without this patch, I will turn back to the original 2.6.15-rc7 an continue
> running this torture test during this night.

The patch should perform slightly better than swiotlb=force
because it will only force bounce buffering 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.

-Andi

  reply	other threads:[~2006-01-03 21: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 [this message]
2006-01-04 10:27       ` Dieter Stüken
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=p737j9hype9.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc="=?iso-8859-1?q?Dieter_St=FCken?= <stueken"@conterra.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