[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 6 Jun 2011 18:15:30 +0300
From: Ohad Ben-Cohen <ohad@...ery.com>
To: "Roedel, Joerg" <Joerg.Roedel@....com>
Cc: "linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"laurent.pinchart@...asonboard.com"
<laurent.pinchart@...asonboard.com>,
"Hiroshi.DOYU@...ia.com" <Hiroshi.DOYU@...ia.com>,
"arnd@...db.de" <arnd@...db.de>,
"davidb@...eaurora.org" <davidb@...eaurora.org>,
Omar Ramirez Luna <omar.ramirez@...com>
Subject: Re: [RFC 0/6] iommu: generic api migration and grouping
Hi Joerg,
On Mon, Jun 6, 2011 at 1:09 PM, Roedel, Joerg <Joerg.Roedel@....com> wrote:
> The IOMMU-API already supports multiple page-sizes. See the
> 'order'-parameter of the map/unmap functions.
This is insufficient; users need somehow to tell what page sizes are
supported by the underlying hardware (we can't assume host page-sizes,
and we want to use bigger pages whenever possible, to relax the TLB
pressure).
>> Further generalizing of iovmm strongly depends on our broader plans for
>> providing a generic virtual memory manager and allocation framework
>> (which, as discussed, should be separated from a specific mapper).
>
> The generic vmm for DMA is called DMA-API :) Any reason for not using
> that (those reasons should be fixed)?
This is definitely something we will look into (dspbridge will need it
too, not only omap3isp).
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists