From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
discuss@x86-64.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes
Date: Mon, 16 Oct 2006 14:21:25 +0200 [thread overview]
Message-ID: <200610161421.25530.ak@suse.de> (raw)
In-Reply-To: <1160133260.1607.60.camel@localhost.localdomain>
On Friday 06 October 2006 13:14, Alan Cox wrote:
> Ar Iau, 2006-10-05 am 23:44 +0200, ysgrifennodd Andi Kleen:
> > I think we had that argument before. IMHO such messages are completely
> > useless. Hangs are not acceptable no matter what messages are printed
> > before.
>
> Oh so you plan to fix the iommu/aacraid problem you always said you
> wouldn't fix ?
They don't cause hangs, just IO errors (or panics if you configure
iommu debugging)
Actually I plan to fix this one, but it will require more work.
Basically the plan is to make the current dma zone variable sized
and get rid of all GFP_DMA allocations. Merge the current soft iommu
with that new dma allocator. Then make sure all allocations
that need such low dma use a mask argument to some allocator.
Then we can have a option to configure the size of the dma low zone.
Users of broken hardware just configure a larger size.
-Andi
next prev parent reply other threads:[~2006-10-16 12:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 17:10 Please pull x86-64 bug fixes Andi Kleen
2006-10-05 17:17 ` Jeff Garzik
2006-10-05 17:31 ` [discuss] " Andi Kleen
2006-10-05 17:43 ` Jeff Garzik
2006-10-05 17:53 ` Andi Kleen
2006-10-05 19:29 ` Jeff Garzik
2006-10-05 19:42 ` Andi Kleen
2006-10-05 20:02 ` Jeff Garzik
2006-10-05 20:10 ` Andi Kleen
2006-10-05 22:45 ` Linus Torvalds
2006-10-05 22:52 ` Andi Kleen
2006-10-05 23:07 ` Linus Torvalds
2006-10-05 23:21 ` Andi Kleen
2006-10-05 23:36 ` Jeff Garzik
2006-10-06 0:57 ` Jeff Garzik
2006-10-06 1:29 ` Linus Torvalds
2006-10-06 11:03 ` Arjan van de Ven
2006-10-06 16:07 ` Linus Torvalds
2006-10-06 16:19 ` Arjan van de Ven
2006-10-06 22:01 ` Rafael J. Wysocki
2006-10-06 22:31 ` Duran, Leo
2006-10-06 23:06 ` Jeff Garzik
2006-10-07 5:23 ` Arjan van de Ven
2006-10-07 2:20 ` Linus Torvalds
2006-10-08 20:59 ` Duran, Leo
2006-10-08 22:42 ` Linus Torvalds
2006-10-05 22:00 ` Alan Cox
2006-10-05 21:44 ` Andi Kleen
2006-10-06 11:14 ` Alan Cox
2006-10-16 12:21 ` Andi Kleen [this message]
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27 ` [discuss] " Andi Kleen
2006-10-05 22:59 ` Linus Torvalds
2006-10-05 23:05 ` Andi Kleen
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=200610161421.25530.ak@suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=discuss@x86-64.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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