From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org,
"cbe-oss-dev@ozlabs.org" <cbe-oss-dev@ozlabs.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Cbe-oss-dev] [PATCH 3/3] Cell IOMMU static mapping support
Date: Tue, 29 Jan 2008 08:37:57 +1100 [thread overview]
Message-ID: <1201556277.6815.194.camel@pasglop> (raw)
In-Reply-To: <20080128214813.GA24416@lixom.net>
On Mon, 2008-01-28 at 15:48 -0600, Olof Johansson wrote:
> > > Does the cell I/O bridge reflect out accesses to 2-4GB on the bus
> > > again? If not, that could be another place to stick the dynamic range
> > > for large config machines.
> >
> > On the PCI bus itself, 2-4GB is where MMIO sits.
>
> Depending on the implementation, 2-4GB accesses _from_ PCI could mean
> something else.
Not on PCI / PCI-X no. Maybe PCI-E could do that sort of ugly hacks but
that wouldn't be within specs I believe.
> But for most machines it doesn't, and I'm guessing cell
> is one of those.
Ben.
next prev parent reply other threads:[~2008-01-28 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 10:45 [PATCH 1/3] Add set_dma_ops() to match get_dma_ops() Michael Ellerman
2008-01-25 10:45 ` [PATCH 3/3] Cell IOMMU static mapping support Michael Ellerman
2008-01-25 13:12 ` [Cbe-oss-dev] " Geert Uytterhoeven
2008-01-26 2:51 ` Olof Johansson
2008-01-28 11:41 ` [Cbe-oss-dev] " Arnd Bergmann
2008-01-28 16:23 ` Olof Johansson
2008-01-28 21:16 ` Benjamin Herrenschmidt
2008-01-28 21:48 ` Olof Johansson
2008-01-28 21:37 ` Benjamin Herrenschmidt [this message]
2008-01-28 21:18 ` Benjamin Herrenschmidt
2008-01-25 10:45 ` [PATCH 2/3] Allocate the hash table under 1G on cell Michael Ellerman
2008-02-05 0:23 ` Benjamin Herrenschmidt
2008-02-05 0:23 ` [PATCH 1/3] Add set_dma_ops() to match get_dma_ops() Benjamin Herrenschmidt
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=1201556277.6815.194.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).