From: Anton Blanchard <anton@samba.org>
To: William Lee Irwin III <wli@holomorphy.com>,
sfr@ozlabs.org, linuxppc64-dev@lists.linuxppc.org,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [PATCH] [ppc64] watch IOMMU virtual merging
Date: Tue, 3 Aug 2004 07:32:30 +1000 [thread overview]
Message-ID: <20040802213230.GP30253@krispykreme> (raw)
In-Reply-To: <20040802170843.GI2334@holomorphy.com>
> This is a rather painful state of affairs. I'm not convinced external
> fragmentation in the IOMMU address space is insurmountable as the
> physically contiguous segments can (in principle; the mechanics of
> ramming this through the IO subsystem are another matter entirely) be
> IO-mapped in a bus-discontiguous fashion.
Yep they can, but if the SG list has been sized to fit after physically
merging then we have a problem when we later on want to split it. If the
architecture had more control over the merging process we could do a
better job here.
> I'm not familiar with the TCE space regions; could you describe or
> point to documentation for the semantics there?
Think of it as a mapping from PCI to host memory, a window of at least
128MB and up to 3GB. You get to carve it up on a page granularity as you
like, we currently create 2 regions, a small allocation region and a
large one (above 15 pages). The aim is to (hopefully) avoid
fragmentation in the large allocation region.
> My first thought is to artificially limit the amount of physical
> merging (hopefully to some nonzero amount instead of disabling it
> entirely) allowed to take place in order to allow for better virtual
> merging.
Removing the large allocation region should also fix our problems. I
should test that to verify its our problem.
Anton
next prev parent reply other threads:[~2004-08-02 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 16:44 [PATCH] [ppc64] watch IOMMU virtual merging Anton Blanchard
2004-08-02 17:08 ` William Lee Irwin III
2004-08-02 21:32 ` Anton Blanchard [this message]
2004-08-02 21:45 ` Benjamin Herrenschmidt
2004-08-02 22:20 ` 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=20040802213230.GP30253@krispykreme \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=sfr@ozlabs.org \
--cc=wli@holomorphy.com \
/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