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
References: <1277355096-15596-1-git-send-email-zpfeffer@codeaurora.org>
Date: Thu, 24 Jun 2010 12:11:56 +0200
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")
Message-ID: <876318ager.fsf@basil.nowhere.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 886
Lines: 24

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/