From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Thu, 17 Jan 2013 10:49:30 +0000 Subject: [PATCH v2] mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls In-Reply-To: <50F61D86.4020801@web.de> References: <20121119144826.f59667b2.akpm@linux-foundation.org> <20130116024014.GH25500@titan.lakedaemon.net> <50F61D86.4020801@web.de> Message-ID: <201301171049.30415.arnd@arndb.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wednesday 16 January 2013, Soeren Moch wrote: > >> I will see what I can do here. Is there an easy way to track the buffer > >> usage without having to wait for complete exhaustion? > > > > DMA_API_DEBUG > > OK, maybe I can try this. > > Any success with this? It should at least tell you if there is a memory leak in one of the drivers. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx110.postini.com [74.125.245.110]) by kanga.kvack.org (Postfix) with SMTP id 0949E6B005D for ; Thu, 17 Jan 2013 05:50:18 -0500 (EST) From: Arnd Bergmann Subject: Re: [PATCH v2] mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls Date: Thu, 17 Jan 2013 10:49:30 +0000 References: <20121119144826.f59667b2.akpm@linux-foundation.org> <20130116024014.GH25500@titan.lakedaemon.net> <50F61D86.4020801@web.de> In-Reply-To: <50F61D86.4020801@web.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201301171049.30415.arnd@arndb.de> Sender: owner-linux-mm@kvack.org List-ID: To: Soeren Moch Cc: Jason Cooper , Greg KH , Thomas Petazzoni , Andrew Lunn , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, Michal Hocko , linux-mm@kvack.org, Kyungmin Park , Mel Gorman , Andrew Morton , Marek Szyprowski , linaro-mm-sig@lists.linaro.org, linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth On Wednesday 16 January 2013, Soeren Moch wrote: > >> I will see what I can do here. Is there an easy way to track the buffer > >> usage without having to wait for complete exhaustion? > > > > DMA_API_DEBUG > > OK, maybe I can try this. > > Any success with this? It should at least tell you if there is a memory leak in one of the drivers. Arnd -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757050Ab3AQKud (ORCPT ); Thu, 17 Jan 2013 05:50:33 -0500 Received: from moutng.kundenserver.de ([212.227.126.171]:63722 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752037Ab3AQKuX (ORCPT ); Thu, 17 Jan 2013 05:50:23 -0500 From: Arnd Bergmann To: Soeren Moch Subject: Re: [PATCH v2] mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls Date: Thu, 17 Jan 2013 10:49:30 +0000 User-Agent: KMail/1.12.2 (Linux/3.7.0-7-generic; KDE/4.3.2; x86_64; ; ) Cc: Jason Cooper , Greg KH , Thomas Petazzoni , Andrew Lunn , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, Michal Hocko , linux-mm@kvack.org, Kyungmin Park , Mel Gorman , Andrew Morton , Marek Szyprowski , linaro-mm-sig@lists.linaro.org, linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth References: <20121119144826.f59667b2.akpm@linux-foundation.org> <20130116024014.GH25500@titan.lakedaemon.net> <50F61D86.4020801@web.de> In-Reply-To: <50F61D86.4020801@web.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201301171049.30415.arnd@arndb.de> X-Provags-ID: V02:K0:VQ8zYUZXF5RKjdlEC5+6M441FcIwh6fUuLSbcm12A2w hEkLLcPWBWqqrI3qQc12FMJIMZ95yEBnM23IpA1oU5EWUBY5Oz 7U1CrzAvN6u2My1A//2snod7CV4L1dwf9x29Kfojx1zr/eUBNr 7LfrWIE3ScvyuO40uF1Jlh6vwTOIdwIAhVxkS6yaMSzS3BvDE+ 1vqaAOcxTuHUm3Si7OoBlgc62IJ76bStz1rd4Pgt8V9MBpNEn6 MNNyiz93iMDLO7kUFsvmRvBDoJtZyIFElVNIHTXCMsYxU+DP6M J7SitH90mq6ubaS8mwX0f4BtPmSia416zROd/4V3Dd19pSY0h6 AbVb8OOq3kIXv88BZank= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 16 January 2013, Soeren Moch wrote: > >> I will see what I can do here. Is there an easy way to track the buffer > >> usage without having to wait for complete exhaustion? > > > > DMA_API_DEBUG > > OK, maybe I can try this. > > Any success with this? It should at least tell you if there is a memory leak in one of the drivers. Arnd