Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754398Ab0GVQdt (ORCPT ); Thu, 22 Jul 2010 12:33:49 -0400 Received: from wolverine01.qualcomm.com ([199.106.114.254]:20903 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751572Ab0GVQdq (ORCPT ); Thu, 22 Jul 2010 12:33:46 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6051"; a="48298847" Date: Thu, 22 Jul 2010 09:33:40 -0700 From: Zach Pfeffer To: FUJITA Tomonori Cc: linux@arm.linux.org.uk, alan@lxorguk.ukuu.org.uk, randy.dunlap@oracle.com, dwalker@codeaurora.org, mel@csn.ul.ie, linux-arm-msm@vger.kernel.org, joro@8bytes.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, andi@firstfloor.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager Message-ID: <20100722163338.GE10255@codeaurora.org> References: <20100713090223.GB20590@n2100.arm.linux.org.uk> <20100714105922D.fujita.tomonori@lab.ntt.co.jp> <20100722035026.GB14176@codeaurora.org> <20100722134708I.fujita.tomonori@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100722134708I.fujita.tomonori@lab.ntt.co.jp> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1190 Lines: 27 On Thu, Jul 22, 2010 at 01:47:36PM +0900, FUJITA Tomonori wrote: > On Wed, 21 Jul 2010 20:50:26 -0700 > Zach Pfeffer 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/