[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100722163338.GE10255@codeaurora.org>
Date: Thu, 22 Jul 2010 09:33:40 -0700
From: Zach Pfeffer <zpfeffer@...eaurora.org>
To: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc: linux@....linux.org.uk, alan@...rguk.ukuu.org.uk,
randy.dunlap@...cle.com, dwalker@...eaurora.org, mel@....ul.ie,
linux-arm-msm@...r.kernel.org, joro@...tes.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 3/3] mm: iommu: The Virtual Contiguous Memory Manager
On Thu, Jul 22, 2010 at 01:47:36PM +0900, FUJITA Tomonori wrote:
> On Wed, 21 Jul 2010 20:50:26 -0700
> Zach Pfeffer <zpfeffer@...eaurora.org> wrote:
>
> > On Wed, Jul 14, 2010 at 10:59:43AM +0900, FUJITA Tomonori wrote:
> > > On Tue, 13 Jul 2010 10:02:23 +0100
> > >
> > > Zach Pfeffer said this new VCM infrastructure can be useful for
> > > video4linux. However, I don't think we need 3,000-lines another
> > > abstraction layer to solve video4linux's issue nicely.
> >
> > Its only 3000 lines because I haven't converted the code to use
> > function pointers.
>
> The main point is adding a new abstraction that don't provide the huge
> benefit.
I disagree. In its current form the API may not be appropriate for
inclusion into the kernel, but it provides a common framework for
handling a class of problems that have been solved many times in the
kernel: large buffer management, IOMMU interoperation and fine grained
mapping control.
--
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