Re: [RFC] mm: iommu: An API to unify IOMMU, CPU and device memory management

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Zach Pfeffer <zpfeffer@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux