[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100721104356S.fujita.tomonori@lab.ntt.co.jp>
Date: Wed, 21 Jul 2010 10:44:37 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: zpfeffer@...eaurora.org
Cc: linux@....linux.org.uk, fujita.tomonori@....ntt.co.jp,
ebiederm@...ssion.com, linux-arch@...r.kernel.org,
dwalker@...eaurora.org, mel@....ul.ie,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, andi@...stfloor.org,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC 1/3 v3] mm: iommu: An API to unify IOMMU, CPU and device
memory management
On Tue, 20 Jul 2010 15:20:01 -0700
Zach Pfeffer <zpfeffer@...eaurora.org> wrote:
> > I'm not saying that it's reasonable to pass (or even allocate) a 1MB
> > buffer via the DMA API.
>
> But given a bunch of large chunks of memory, is there any API that can
> manage them (asked this on the other thread as well)?
What is the problem about mapping a 1MB buffer with the DMA API?
Possibly, an IOMMU can't find space for 1MB but it's not the problem
of the DMA API.
--
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