Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758661Ab0GTTi0 (ORCPT ); Tue, 20 Jul 2010 15:38:26 -0400 Received: from wolverine01.qualcomm.com ([199.106.114.254]:56496 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751429Ab0GTTiX (ORCPT ); Tue, 20 Jul 2010 15:38:23 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6049"; a="48077288" Subject: Re: [PATCH 2/4] mm: cma: Contiguous Memory Allocator added From: Daniel Walker To: =?UTF-8?Q?Micha=C5=82?= Nazarewicz Cc: linux-mm@kvack.org, Marek Szyprowski , Pawel Osciak , Xiaolin Zhang , Hiremath Vaibhav , Robert Fekete , Marcus Lorentzon , linux-kernel@vger.kernel.org, Kyungmin Park , linux-arm-msm@vger.kernel.org In-Reply-To: References: <1279649724.26765.23.camel@c-dwalke-linux.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 20 Jul 2010 12:38:18 -0700 Message-ID: <1279654698.26765.31.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3024 Lines: 72 On Tue, 2010-07-20 at 21:14 +0200, Michał Nazarewicz wrote: > On Tue, 20 Jul 2010 20:15:24 +0200, Daniel Walker wrote: > > > On Tue, 2010-07-20 at 17:51 +0200, Michal Nazarewicz wrote: > >> +** Use cases > >> + > >> + Lets analyse some imaginary system that uses the CMA to see how > >> + the framework can be used and configured. > >> + > >> + > >> + We have a platform with a hardware video decoder and a camera > >> each > >> + needing 20 MiB of memory in worst case. Our system is written in > >> + such a way though that the two devices are never used at the same > >> + time and memory for them may be shared. In such a system the > >> + following two command line arguments would be used: > >> + > >> + cma=r=20M cma_map=video,camera=r > > > > This seems inelegant to me.. It seems like these should be connected > > with the drivers themselves vs. doing it on the command like for > > everything. You could have the video driver declare it needs 20megs, and > > the the camera does the same but both indicate it's shared .. > > > > If you have this disconnected from the drivers it will just cause > > confusion, since few will know what these parameters should be for a > > given driver set. It needs to be embedded in the kernel. > > I see your point but the problem is that devices drivers don't know the > rest of the system neither they know what kind of use cases the system > should support. > > > Lets say, we have a camera, a JPEG encoder, a video decoder and > scaler (ie. devices that scales raw image). We want to support the > following 3 use cases: > > 1. Camera's output is scaled and displayed in real-time. > 2. Single frame is taken from camera and saved as JPEG image. > 3. A video file is decoded, scaled and displayed. > > What is apparent is that camera and video decoder are never running > at the same time. The same situation is with JPEG encoder and scaler. > From this knowledge we can construct the following: > > cma=a=10M;b=10M cma_map=camera,video=a;jpeg,scaler=b It should be implicit tho. If the video driver isn't using the memory then it should tell your framework that the memory is not used. That way something else can use it. (btw, these strings your creating yikes, talk about confusing ..) > One of the purposes of the CMA framework is to make it let device > drivers completely forget about the memory management and enjoy > a simple API. The driver, and it's maintainer, are really the best people to know how much memory they need and when it's used/unused. You don't really want to architect them out. Daniel -- Sent by an consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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/