From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by kanga.kvack.org (Postfix) with ESMTP id 1B5AF6B0038 for ; Mon, 16 Mar 2015 21:43:06 -0400 (EDT) Received: by padcy3 with SMTP id cy3so81701023pad.3 for ; Mon, 16 Mar 2015 18:43:05 -0700 (PDT) Received: from lgemrelse6q.lge.com (LGEMRELSE6Q.lge.com. [156.147.1.121]) by mx.google.com with ESMTP id b5si25914298pdo.198.2015.03.16.18.43.04 for ; Mon, 16 Mar 2015 18:43:05 -0700 (PDT) Date: Tue, 17 Mar 2015 10:43:06 +0900 From: Joonsoo Kim Subject: Re: [PATCH v4 0/5] mm: cma: add some debug information for CMA Message-ID: <20150317014306.GB19483@js1304-P5Q-DELUXE> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Stefan Strogin Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , Marek Szyprowski , Michal Nazarewicz , aneesh.kumar@linux.vnet.ibm.com, Laurent Pinchart , Dmitry Safonov , Pintu Kumar , Weijie Yang , Laura Abbott , SeongJae Park , Hui Zhu , Minchan Kim , Dyasly Sergey , Vyacheslav Tyrtov , Aleksei Mateosian , gregory.0xf0@gmail.com, sasha.levin@oracle.com, gioh.kim@lge.com, pavel@ucw.cz, stefan.strogin@gmail.com On Mon, Mar 16, 2015 at 07:06:55PM +0300, Stefan Strogin wrote: > Hi all. > > Here is the fourth version of a patch set that adds some debugging facility for > CMA. > > This patch set is based on next-20150316. > It is also available on git: > git://github.com/stefanstrogin/linux -b cmainfo-v4 > > We want an interface to see a list of currently allocated CMA buffers and some > useful information about them (like /proc/vmallocinfo but for physically > contiguous buffers allocated with CMA). > > For example. We want a big (megabytes) CMA buffer to be allocated in runtime > in default CMA region. If someone already uses CMA then the big allocation > could fail. If it happened then with such an interface we could find who used > CMA at the moment of failure, who caused fragmentation and so on. Ftrace also > would be helpful here, but with ftrace we can see the whole history of > allocations and releases, whereas with this patch set we can see a snapshot of > CMA region with actual information about its allocations. Hello, Hmm... I still don't think that this is really helpful to find root cause of fragmentation. Think about following example. Assume 1024 MB CMA region. 128 MB allocation * 4 1 MB allocation 128 MB allocation 128 MB release * 4 (first 4) try 512 MB allocation With above sequences, fragmentation happens and 512 MB allocation would be failed. We can get information about 1 MB allocation and 128 MB one from the buffer list as you suggested, but, fragmentation are related to whole sequence of allocation/free history, not snapshot of allocation. Thanks. -- 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