All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wang Sheng-Hui" <shhuiw@foxmail.com>
To: "Minchan Kim" <minchan@kernel.org>
Cc: akpm <akpm@linux-foundation.org>,
	mgorman <mgorman@techsingularity.net>,
	"iamjoonsoo.kim" <iamjoonsoo.kim@lge.com>,
	linux-mm <linux-mm@kvack.org>, "Vlastimil Babka" <vbabka@suse.cz>
Subject: Re:  Why __alloc_contig_migrate_range calls  migrate_prep() at first?
Date: Wed, 1 Jun 2016 20:11:41 +0800	[thread overview]
Message-ID: <tencent_67BF47520FE5A3977D2A212F@qq.com> (raw)

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

Minchan,

That sounds good to me. 

Thanks,
Wang Sheng-Hui


------------------ Original ------------------
From:  "Minchan Kim";<minchan@kernel.org>;
Date:  Wed, Jun 1, 2016 03:40 PM
To:  "Wang Sheng-Hui"<shhuiw@foxmail.com>; 
Cc:  "akpm"<akpm@linux-foundation.org>; "mgorman"<mgorman@techsingularity.net>; "iamjoonsoo.kim"<iamjoonsoo.kim@lge.com>; "linux-mm"<linux-mm@kvack.org>; "Vlastimil Babka"<vbabka@suse.cz>; 
Subject:  Re: Why __alloc_contig_migrate_range calls  migrate_prep() at first?



On Wed, Jun 01, 2016 at 11:42:29AM +0800, Wang Sheng-Hui wrote:
> Dear,
> 
> Sorry to trouble you.
> 
> I noticed cma_alloc would turn to  __alloc_contig_migrate_range for allocating pages.
> But  __alloc_contig_migrate_range calls  migrate_prep() at first, even if the requested page
> is single and free, lru_add_drain_all still run (called by  migrate_prep())?
> 
> Image a large chunk of free contig pages for CMA, various drivers may request a single page from
> the CMA area, we'll get  lru_add_drain_all run for each page.
> 
> Should we detect if the required pages are free before migrate_prep(), or detect at least for single 
> page allocation?

That makes sense to me.

How about calling migrate_prep once migrate_pages fails in the first trial?

diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 9d666df5ef95..c504c1a623d2 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -6623,8 +6623,6 @@ static int __alloc_contig_migrate_range(struct compact_control *cc,
unsigned int tries = 0;
int ret = 0;

- migrate_prep();
-
while (pfn < end || !list_empty(&cc->migratepages)) {
if (fatal_signal_pending(current)) {
ret = -EINTR;
@@ -6650,6 +6648,8 @@ static int __alloc_contig_migrate_range(struct compact_control *cc,

ret = migrate_pages(&cc->migratepages, alloc_migrate_target,
 NULL, 0, cc->mode, MR_CMA);
+if (ret)
+ migrate_prep();
}
if (ret < 0) {
putback_movable_pages(&cc->migratepages);


> 
> ------------------
> Regards,
> Wang Sheng-HuiN‹§²æìr¸›zǧu©ž²Æ {­†éì¹»®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸¢¹¨­è§~Š'.)îÄ

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

             reply	other threads:[~2016-06-01 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 12:11 Wang Sheng-Hui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-01  3:42 Why __alloc_contig_migrate_range calls migrate_prep() at first? Wang Sheng-Hui
2016-06-01  7:40 ` Minchan Kim
2016-06-02  1:19   ` Wang Sheng-Hui
2016-06-02  2:22     ` Joonsoo Kim
2016-06-02  4:29       ` Minchan Kim
2016-06-02  6:29         ` Joonsoo Kim
2016-06-02  6:46           ` Minchan Kim

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=tencent_67BF47520FE5A3977D2A212F@qq.com \
    --to=shhuiw@foxmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@kernel.org \
    --cc=vbabka@suse.cz \
    /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.