From: Andi Kleen <andi@firstfloor.org>
To: Zach Pfeffer <zpfeffer@codeaurora.org>
Cc: mel@csn.ul.ie, dwalker@codeaurora.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [RFC] mm: iommu: An API to unify IOMMU, CPU and device memory management
Date: Thu, 24 Jun 2010 12:11:56 +0200 [thread overview]
Message-ID: <876318ager.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1277355096-15596-1-git-send-email-zpfeffer@codeaurora.org> (Zach Pfeffer's message of "Wed, 23 Jun 2010 21:51:36 -0700")
Zach Pfeffer <zpfeffer@codeaurora.org> writes:
> This patch contains the documentation for and the main header file of
> the API, termed the Virtual Contiguous Memory Manager. Its use would
> allow all of the IOMMU to VM, VM to device and device to IOMMU
> interoperation code to be refactored into platform independent code.
I read all the description and it's still unclear what advantage
this all has over the current architecture?
At least all the benefits mentioned seem to be rather nebulous.
Can you describe a concrete use case that is improved by this code
directly?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
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:[~2010-06-24 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 4:51 Zach Pfeffer
2010-06-24 10:11 ` Andi Kleen [this message]
2010-06-25 6:48 ` Zach Pfeffer
2010-06-27 4:46 ` FUJITA Tomonori
2010-06-28 21:16 ` Zach Pfeffer
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=876318ager.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-omap@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=zpfeffer@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox