From: Andi Kleen <andi@firstfloor.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: Tue, 18 Oct 2011 08:56:14 -0700 [thread overview]
Message-ID: <m2ehyaz42p.fsf@firstfloor.org> (raw)
In-Reply-To: <20111018154828.GA4201@homer.localdomain> (Jerome Glisse's message of "Tue, 18 Oct 2011 11:48:28 -0400")
Jerome Glisse <j.glisse@gmail.com> writes:
>
> 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 ?
I don't think relying on this is very wise. Better add some way to unmap
when space is running short.
-Andi
next prev parent reply other threads:[~2011-10-18 15:56 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 [this message]
2011-10-18 16:09 ` Jerome Glisse
2011-10-20 8:00 ` 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=m2ehyaz42p.fsf@firstfloor.org \
--to=andi@firstfloor.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.