From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: IOMMU keeping mapping over long period of time
Date: Thu, 20 Oct 2011 10:00:00 +0200 [thread overview]
Message-ID: <1319097600.29415.568.camel@pasglop> (raw)
In-Reply-To: <20111018154828.GA4201@homer.localdomain>
On Tue, 2011-10-18 at 11:48 -0400, Jerome Glisse wrote:
> Hi,
>
> For GPU we are entertaining the idea of keeping pci/dma mapping of page
> around for the whole life span of GPU object (which can be as long as
> the computer uptime). Here we are talking about possibly several GB of
> data.
>
> GPU for which we are interested have dma mask of 40bits at least, thus
> they can work with high mem page. My main concern is when an iommu is
> active, such amount of continuously mapped page might exhaust the iommu
> address space. My understanding is that Intel & AMD iommu are capable of
> growing their address space but is it somethings we can rely on ?
This will be problematic on other platforms. Also keep in mind that
objects mapped in the iommu can no longer be swapped out.
It might be useful to have a more 'lazy' mechanism where objects are
kept mapped but with a callback to unmap them in case of iommu pressure.
The problem of course with such a scheme is that it requires iommu
object tracking and horrible locking issues.
Ben.
prev parent reply other threads:[~2011-10-20 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 15:48 IOMMU keeping mapping over long period of time Jerome Glisse
2011-10-18 15:56 ` Andi Kleen
2011-10-18 16:09 ` Jerome Glisse
2011-10-20 8:00 ` Benjamin Herrenschmidt [this message]
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=1319097600.29415.568.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=iommu@lists.linux-foundation.org \
--cc=j.glisse@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.