From: David Miller <davem@davemloft.net>
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: muli@il.ibm.com
Cc: mgross@linux.intel.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH]intel-iommu batched iotlb flushes
Date: Tue, 12 Feb 2008 01:00:06 -0800 (PST)
Date: Tue, 12 Feb 2008 10:52:56 +0200 [thread overview]
Message-ID: <20080212.010006.255202479.davem@davemloft.net> (raw)
In-Reply-To: <20080212085256.GF5750@rhun.haifa.ibm.com>
> The streaming DMA-API was designed to conserve IOMMU mappings for
> machines where IOMMU mappings are a scarce resource, and is a poor
> fit for a modern IOMMU such as VT-d with a 64-bit IO address space
> (or even an IOMMU with a 32-bit address space such as Calgary) where
> there are plenty of IOMMU mappings available.
For the 64-bit case what you are suggesting eventually amounts
to mapping all available RAM in the IOMMU.
Although an extreme version of your suggestion, it would be the
most efficient as it would require zero IOMMU flush operations.
But we'd lose things like protection and other benefits.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-12 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 22:41 [PATCH]intel-iommu batched iotlb flushes mark gross
2008-02-11 23:27 ` Randy Dunlap
2008-02-12 16:05 ` mark gross
2008-02-12 16:34 ` Randy Dunlap
2008-02-12 19:55 ` mark gross
2008-02-12 20:21 ` Randy Dunlap
2008-02-13 18:10 ` mark gross
2008-02-13 18:23 ` Randy Dunlap
2008-02-13 19:35 ` mark gross
2008-02-12 8:52 ` Muli Ben-Yehuda
2008-02-12 9:00 ` David Miller, Muli Ben-Yehuda [this message]
2008-02-12 9:07 ` Muli Ben-Yehuda
2008-02-12 15:54 ` mark gross
2008-02-12 23:46 ` David Miller, mark gross
2008-02-13 18:31 ` mark gross
2008-02-12 15:37 ` mark gross
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=20080212.010006.255202479.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgross@linux.intel.com \
--cc=muli@il.ibm.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;
as well as URLs for NNTP newsgroup(s).