All of lore.kernel.org
 help / color / mirror / Atom feed
From: pintu_agarwal <pintu_agarwal@yahoo.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	linux-arm-kernel@lists.infradead.org,
	linaro-mm-sig@lists.linaro.org, ritesh.list@gmail.com
Cc: pintu.k@outlook.com, "pintu.k@samsung.com" <pintu.k@samsung.com>,
	vishu_1385@yahoo.com, m.szyprowski@samsung.com,
	mina86@mina86.com, ngupta@vflare.org, iqbalblr@gmail.com
Subject: RE: [linux-3.10.17] Could not allocate memory from free CMA areas
Date: Mon, 04 Aug 2014 00:24:12 +0900	[thread overview]
Message-ID: <54sabdnxop04vxd7ewndc0qf.1407077745645@email.android.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]

Dear Joonsoo,

I tried your changes which are present at the below link. 
https://github.com/JoonsooKim/linux/tree/cma-fix-up-v3.0-next-20140625
But unfortunately for me it did not help much. 
After running various apps that uses ION nonmovable memory, it fails to allocate memory after some time. When I see the pagetypeinfo shows lots of CMA pages available and non-movable were very less and thus nonmovable allocation were failing.
However I noticed the failure was little delayed. 
Also I noticed that the CMA utilized and the CMA free is not matching with total CMA size.

In my system RAM is 256MB and CMA configured is 56MB.
And free memory was hanging around 30-40MB during failure.

Am I missing something? 
My kernel version is 3.10 and I applied the changes manually. 
If there are other sets of patches that needs to be applied,  please let me know.
Note, I did not apply the ALLOC_CMA removal patches. 

Now I am experimenting more and will share if I have any findings.

Thank you!
Pintu

Sent from Samsung Mobile

-------- Original message --------
From: Joonsoo Kim <iamjoonsoo.kim@lge.com> 
Date: 29/07/2014  5:06 PM  (GMT+09:00) 
To: 'pintu_agarwal' <pintu_agarwal@yahoo.com>,linux-mm@kvack.org,linux-arm-kernel@lists.infradead.org,linaro-mm-sig@lists.linaro.org,ritesh.list@gmail.com 
Cc: pintu.k@outlook.com,pintu.k@samsung.com,vishu_1385@yahoo.com,m.szyprowski@samsung.com,mina86@mina86.com,ngupta@vflare.org,iqbalblr@gmail.com 
Subject: RE: [linux-3.10.17] Could not allocate memory from free CMA areas 
 


From: pintu_agarwal [mailto:pintu_agarwal@yahoo.com] 
Sent: Friday, July 25, 2014 12:15 AM
To: PINTU KUMAR; linux-mm@kvack.org; linux-arm-kernel@lists.infradead.org; linaro-mm-sig@lists.linaro.org; iamjoonsoo.kim@lge.com; ritesh.list@gmail.com
Cc: pintu.k@outlook.com; pintu.k@samsung.com; vishu_1385@yahoo.com; m.szyprowski@samsung.com; mina86@mina86.com; ngupta@vflare.org; iqbalblr@gmail.com
Subject: RE: [linux-3.10.17] Could not allocate memory from free CMA areas

Dear joonsoo kim,

> I have your patches for: Aggressively allocate memory from cma ....
> We are facing almost similar problem here.
> If any of your patches still working for you please let us know here.
> I would like to try those approach.


Hello,

I stopped to implement it, because there are other bugs on CMA related codes.
Although aggressively allocate... doesn't have bugs itself, it enlarges
existing freepage counting bugs significantly so I'm first trying to fix
those bugs. See the below link.

https://lkml.org/lkml/2014/7/4/79

I will restart to implement aggressively... after fixing these bugs.

If you have interest on next version of aggressively allocate..., see the
following link.

https://github.com/JoonsooKim/linux/tree/cma-fix-up-v3.0-next-20140625

Thanks.



[-- Attachment #2: Type: text/html, Size: 3476 bytes --]

             reply	other threads:[~2014-08-03 15:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 15:24 pintu_agarwal [this message]
2014-08-04  7:11 ` [linux-3.10.17] Could not allocate memory from free CMA areas Joonsoo Kim
2014-08-04  7:11   ` Joonsoo Kim
2014-08-05 14:54   ` Pintu Kumar
2014-08-05 14:54     ` Pintu Kumar
2014-08-06  7:59     ` Joonsoo Kim
2014-08-06  7:59       ` Joonsoo Kim
  -- strict thread matches above, loose matches on Subject: below --
2014-07-24 15:15 pintu_agarwal
2014-07-29  8:06 ` Joonsoo Kim
2014-07-29  8:06   ` Joonsoo Kim
2014-07-08 23:41 PINTU KUMAR
2014-07-08 23:41 ` PINTU KUMAR
2014-07-12  1:27 ` Pintu Kumar
2014-07-12  1:27   ` Pintu Kumar
2014-07-15 12:49 ` Marek Szyprowski
2014-07-15 12:49   ` Marek Szyprowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54sabdnxop04vxd7ewndc0qf.1407077745645@email.android.com \
    --to=pintu_agarwal@yahoo.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=iqbalblr@gmail.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mina86@mina86.com \
    --cc=ngupta@vflare.org \
    --cc=pintu.k@outlook.com \
    --cc=pintu.k@samsung.com \
    --cc=ritesh.list@gmail.com \
    --cc=vishu_1385@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.