linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Joonsoo Kim" <iamjoonsoo.kim@lge.com>
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
Date: Tue, 29 Jul 2014 17:06:59 +0900	[thread overview]
Message-ID: <010401cfab04$1536b740$3fa425c0$@lge.com> (raw)
In-Reply-To: <dsqnq2i1mer1r7kpvuflt0k9.1406214301636@email.android.com>



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.


--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-07-29  8:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 15:15 [linux-3.10.17] Could not allocate memory from free CMA areas pintu_agarwal
2014-07-29  8:06 ` Joonsoo Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-03 15:24 pintu_agarwal
2014-08-04  7:11 ` Joonsoo Kim
2014-08-05 14:54   ` Pintu Kumar
2014-08-06  7:59     ` Joonsoo Kim
2014-07-08 23:41 PINTU KUMAR
2014-07-12  1:27 ` Pintu Kumar
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='010401cfab04$1536b740$3fa425c0$@lge.com' \
    --to=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=pintu_agarwal@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).