From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/2] POWERPC: Lower threshold for DART enablement to 1GB, V2
Date: Fri, 14 Apr 2006 06:51:55 +1000 [thread overview]
Message-ID: <1144961515.4935.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20060413160712.GG24769@pb15.lixom.net>
On Thu, 2006-04-13 at 11:07 -0500, Olof Johansson wrote:
> On Thu, Apr 13, 2006 at 08:45:49PM +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2006-04-13 at 09:40 +0300, Muli Ben-Yehuda wrote:
> > > On Wed, Apr 12, 2006 at 09:52:33PM -0500, Olof Johansson wrote:
> > >
> > > > iommu=off can still be used for those who don't want to deal with the
> > > > overhead (and don't need it for any devices).
> > >
> > > I've been pondering walking the PCI bus before deciding to enable an
> > > IOMMU and checking each device's DMA mask. Is this something that you
> > > considered and rejected, or just something no one got around to doing?
> >
> > It would do the trick for airport cards in G5s.. a little bit of OF
> > walking to find the card.
>
> Walking the DT means we need to hardcode it on PCI IDs, since the Apple
> OF doesn't give the Airport device a logical name. It's probably easier
> to implement than walking PCI, but we'd need to maintain a table. My
> vote is for PCI walking, I'll give that a shot over the weekend.
PCI walking it soo late to decide wether to enable the DART no ? In any
case, we need a table, so I wouldn't bother with PCI walking here.
Anyway... we should be able to have almost no perf. degradation or even
an improvement with the DART thanks to virtual merging. Currently, we
pay a cost due to our stupid invalidate mecanism that we should really
fix by shooting the TLB directly. Also have you made sure all your
additions for handling crappy hardware are nicely wrapped in unlikely()
statements ? :)
> > It won't help with cardbus broadcom's but then, there is currently no G5
> > with a cardbus adaptor that I know of :) It's possible I suppose to get
> > a pci<->cardbus adapter but I suppose in that case, we can ignore it ...
>
> Yep, that should be rare enough.
next prev parent reply other threads:[~2006-04-13 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 2:05 [PATCH] [1/2] POWERPC: IOMMU support for honoring dma_mask Olof Johansson
2006-04-13 2:28 ` [PATCH] [2/2] POWERPC: Lower threshold for DART enablement to 1GB Olof Johansson
2006-04-13 2:52 ` [PATCH] [2/2] POWERPC: Lower threshold for DART enablement to 1GB, V2 Olof Johansson
2006-04-13 6:40 ` Muli Ben-Yehuda
2006-04-13 10:45 ` Benjamin Herrenschmidt
2006-04-13 16:07 ` Olof Johansson
2006-04-13 17:31 ` Muli Ben-Yehuda
2006-04-13 20:52 ` Benjamin Herrenschmidt
2006-04-14 14:48 ` Muli Ben-Yehuda
2006-04-14 20:57 ` Benjamin Herrenschmidt
2006-04-15 7:45 ` Muli Ben-Yehuda
2006-04-15 13:09 ` Jimi Xenidis
2006-04-15 13:37 ` Jon Mason
2006-04-15 20:28 ` Benjamin Herrenschmidt
2006-04-13 20:51 ` Benjamin Herrenschmidt [this message]
2006-04-13 22:27 ` Olof Johansson
2006-04-13 22:38 ` Benjamin Herrenschmidt
2006-04-13 15:57 ` Olof Johansson
2006-04-14 18:55 ` [PATCH] [1/2] POWERPC: IOMMU support for honoring dma_mask Olof Johansson
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=1144961515.4935.22.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.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).