linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: zhang.mingjun@linaro.org
Cc: minchan@kernel.org, m.szyprowski@samsung.com,
	akpm@linux-foundation.org, haojian.zhuang@linaro.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mingjun Zhang <troy.zhangmingjun@linaro.org>
Subject: Re: [PATCH] mm: cma: free cma page to buddy instead of being cpu hot page
Date: Tue, 29 Oct 2013 09:33:23 +0000	[thread overview]
Message-ID: <20131029093322.GA2400@suse.de> (raw)
In-Reply-To: <1382960569-6564-1-git-send-email-zhang.mingjun@linaro.org>

On Mon, Oct 28, 2013 at 07:42:49PM +0800, zhang.mingjun@linaro.org wrote:
> From: Mingjun Zhang <troy.zhangmingjun@linaro.org>
> 
> free_contig_range frees cma pages one by one and MIGRATE_CMA pages will be
> used as MIGRATE_MOVEABLE pages in the pcp list, it causes unnecessary
> migration action when these pages reused by CMA.
> 
> Signed-off-by: Mingjun Zhang <troy.zhangmingjun@linaro.org>
> ---
>  mm/page_alloc.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 0ee638f..84b9d84 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1362,7 +1362,8 @@ void free_hot_cold_page(struct page *page, int cold)
>  	 * excessively into the page allocator
>  	 */
>  	if (migratetype >= MIGRATE_PCPTYPES) {
> -		if (unlikely(is_migrate_isolate(migratetype))) {
> +		if (unlikely(is_migrate_isolate(migratetype))
> +			|| is_migrate_cma(migratetype))
>  			free_one_page(zone, page, 0, migratetype);
>  			goto out;

This slightly impacts the page allocator free path for a marginal gain
on CMA which are relatively rare allocations. There is no obvious
benefit to this patch as I expect CMA allocations to flush the PCP lists
when a range of pages have been isolated and migrated. Is there any
measurable benefit to this patch?

-- 
Mel Gorman
SUSE Labs

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

  parent reply	other threads:[~2013-10-29  9:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 11:42 [PATCH] mm: cma: free cma page to buddy instead of being cpu hot page zhang.mingjun
2013-10-28 16:04 ` Laura Abbott
2013-10-29  4:54 ` Minchan Kim
2013-10-29  6:41   ` KOSAKI Motohiro
2013-10-29  7:00   ` Zhang Mingjun
2013-10-29  7:25     ` Minchan Kim
2013-10-29 11:17       ` Zhang Mingjun
2013-10-29  9:33 ` Mel Gorman [this message]
2013-10-29 11:49   ` Zhang Mingjun
2013-10-29 12:27     ` Mel Gorman
2013-10-29 15:02       ` Zhang Mingjun
2013-10-29 16:14         ` Laura Abbott
2013-10-30  5:40           ` Minchan Kim
2013-10-31  2:14             ` Laura Abbott
2013-11-01  1:49               ` Minchan Kim
2013-12-23 12:38             ` Wanpeng Li
2013-10-30  2:55         ` Minchan Kim
2013-11-05 21:44   ` Andrew Morton
2013-11-06  6:43     ` Minchan Kim
2013-11-06 23:41       ` Andrew Morton

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=20131029093322.GA2400@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=haojian.zhuang@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=minchan@kernel.org \
    --cc=troy.zhangmingjun@linaro.org \
    --cc=zhang.mingjun@linaro.org \
    /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).