All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: CMA and zone watermarks
Date: Tue, 09 Oct 2012 02:37:46 +0200	[thread overview]
Message-ID: <507371DA.9080309@samsung.com> (raw)
In-Reply-To: <CAH+eYFCJTtF+FeqKs_ho5yyX0tkUBoaa-yfsd1rVshcQ5Xxp=A@mail.gmail.com>

Hello,

On 10/8/2012 5:41 PM, Rabin Vincent wrote:

> It appears that when CMA is enabled, the zone watermarks are not properly
> respected, leading to for example GFP_NOWAIT allocations getting access to the
> high pools.
>
> I ran the following test code which simply allocates pages with GFP_NOWAIT
> until it fails, and then tries GFP_ATOMIC.  Without CMA, the GFP_ATOMIC
> allocation succeeds, with CMA, it fails too.

Could You run your test with latest linux-next kernel? There have been 
some patches merged to akpm tree which should fix accounting for free 
and free cma pages. I hope it should fix this issue.

Best regards
-- 
Marek Szyprowski
Samsung Poland R&D Center

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: CMA and zone watermarks
Date: Tue, 09 Oct 2012 02:37:46 +0200	[thread overview]
Message-ID: <507371DA.9080309@samsung.com> (raw)
In-Reply-To: <CAH+eYFCJTtF+FeqKs_ho5yyX0tkUBoaa-yfsd1rVshcQ5Xxp=A@mail.gmail.com>

Hello,

On 10/8/2012 5:41 PM, Rabin Vincent wrote:

> It appears that when CMA is enabled, the zone watermarks are not properly
> respected, leading to for example GFP_NOWAIT allocations getting access to the
> high pools.
>
> I ran the following test code which simply allocates pages with GFP_NOWAIT
> until it fails, and then tries GFP_ATOMIC.  Without CMA, the GFP_ATOMIC
> allocation succeeds, with CMA, it fails too.

Could You run your test with latest linux-next kernel? There have been 
some patches merged to akpm tree which should fix accounting for free 
and free cma pages. I hope it should fix this issue.

Best regards
-- 
Marek Szyprowski
Samsung Poland R&D Center

  reply	other threads:[~2012-10-09  0:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 15:41 CMA and zone watermarks Rabin Vincent
2012-10-09  0:37 ` Marek Szyprowski [this message]
2012-10-09  0:37   ` Marek Szyprowski
2012-10-09 15:25   ` Rabin Vincent
2012-10-09 15:25     ` Rabin Vincent
2012-10-09  3:10 ` Minchan Kim
2012-10-09  3:10   ` Minchan Kim
2012-10-09  3:12   ` Marek Szyprowski
2012-10-09  3:12     ` Marek Szyprowski
2012-10-09  4:43     ` Minchan Kim
2012-10-09  4:43       ` Minchan Kim
2012-10-09  4:53       ` Marek Szyprowski
2012-10-09  4:53         ` Marek Szyprowski
2012-10-09  5:07         ` Minchan Kim
2012-10-09  5:07           ` Minchan Kim
2012-10-09  5:16           ` Marek Szyprowski
2012-10-09  5:16             ` 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=507371DA.9080309@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rabin@rab.in \
    /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.