Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754023Ab1FNVBb (ORCPT ); Tue, 14 Jun 2011 17:01:31 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:49630 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753517Ab1FNVBa (ORCPT ); Tue, 14 Jun 2011 17:01:30 -0400 X-IronPort-AV: E=McAfee;i="5400,1158,6377"; a="97510782" Message-ID: <4DF7CC22.6050602@codeaurora.org> Date: Tue, 14 Jun 2011 15:01:22 -0600 From: Jordan Crouse User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: Arnd Bergmann CC: Zach Pfeffer , linux-arm-kernel@lists.infradead.org, Daniel Walker , Daniel Stone , linux-mm@kvack.org, Mel Gorman , linux-kernel@vger.kernel.org, Michal Nazarewicz , linaro-mm-sig@lists.linaro.org, Jesse Barker , Kyungmin Park , Ankita Garg , Andrew Morton , KAMEZAWA Hiroyuki , linux-media@vger.kernel.org Subject: Re: [Linaro-mm-sig] [PATCH 08/10] mm: cma: Contiguous Memory Allocator added References: <1307699698-29369-1-git-send-email-m.szyprowski@samsung.com> <20110614170158.GU2419@fooishbar.org> <201106142242.25157.arnd@arndb.de> In-Reply-To: <201106142242.25157.arnd@arndb.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1193 Lines: 24 On 06/14/2011 02:42 PM, Arnd Bergmann wrote: > On Tuesday 14 June 2011 20:58:25 Zach Pfeffer wrote: >> I've seen this split bank allocation in Qualcomm and TI SoCs, with >> Samsung, that makes 3 major SoC vendors (I would be surprised if >> Nvidia didn't also need to do this) - so I think some configurable >> method to control allocations is necessarily. The chips can't do >> decode without it (and by can't do I mean 1080P and higher decode is >> not functionally useful). Far from special, this would appear to be >> the default. > > Thanks for the insight, that's a much better argument than 'something > may need it'. Are those all chips without an IOMMU or do we also > need to solve the IOMMU case with split bank allocation? Yes. The IOMMU case with split bank allocation is key, especially for shared buffers. Consider the case where video is using a certain bank for performance purposes and that frame is shared with the GPU. Jordan -- 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/