From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Anton Blanchard <anton@samba.org>,
sfr@ozlabs.org,
linuxppc64-dev <linuxppc64-dev@lists.linuxppc.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [ppc64] watch IOMMU virtual merging
Date: Tue, 03 Aug 2004 07:45:51 +1000 [thread overview]
Message-ID: <1091483151.7389.78.camel@gaston> (raw)
In-Reply-To: <20040802170843.GI2334@holomorphy.com>
> I'm not familiar with the TCE space regions; could you describe or
> point to documentation for the semantics there?
>
> 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.
Actually, we could tune the ratio between large allocs and small allocs,
the real problem is the failure case. We can't really afford to break
down a physical segment at the iommu level because that would increase
the size of the SG list which can't be dealt at the upper level (we don't
know how much space has been allocated and the HW may have limitations on
the number of entries).
What we really need is a way for drivers to return the BIO upstream and
ask for a split in case of iommu allocation error, but I've been told that
would be horribly complex...
Ben.
next prev parent reply other threads:[~2004-08-02 21:51 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
2004-08-02 21:45 ` Benjamin Herrenschmidt [this message]
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=1091483151.7389.78.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=anton@samba.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