linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Pintu Kumar <pintu.k@samsung.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, iamjoonsoo.kim@lge.com, mhocko@suse.cz,
	riel@redhat.com, emunson@akamai.com, mgorman@suse.de,
	zhangyanfei@cn.fujitsu.com, rientjes@google.com
Cc: cpgs@samsung.com, pintu_agarwal@yahoo.com, pintu.k@outlook.com,
	vishnu.ps@samsung.com, rohit.kr@samsung.com
Subject: Re: [PATCH 1/1] mm: compaction: include compact_nodes in compaction.h
Date: Fri, 7 Aug 2015 16:18:02 +0200	[thread overview]
Message-ID: <55C4BE1A.8050408@suse.cz> (raw)
In-Reply-To: <1438956233-28690-1-git-send-email-pintu.k@samsung.com>

On 08/07/2015 04:03 PM, Pintu Kumar wrote:
> This patch declares compact_nodes prototype in compaction.h
> header file.
> This will allow us to call compaction from other places.
> For example, during system suspend, suppose we want to check
> the fragmentation state of the system. Then based on certain
> threshold, we can invoke compaction, when system is idle.
> There could be other use cases.

Isn't it more common to introduce such visibility changes only as part 
of series that actually benefit from it?

Otherwise next month somebody might notice that it's unused outside 
compaction.c and send a cleanup patch to make it static again...

> Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
> ---
>   include/linux/compaction.h |    2 +-
>   mm/compaction.c            |    2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/compaction.h b/include/linux/compaction.h
> index aa8f61c..800ff50 100644
> --- a/include/linux/compaction.h
> +++ b/include/linux/compaction.h
> @@ -50,7 +50,7 @@ extern bool compaction_deferred(struct zone *zone, int order);
>   extern void compaction_defer_reset(struct zone *zone, int order,
>   				bool alloc_success);
>   extern bool compaction_restarting(struct zone *zone, int order);
> -
> +extern void compact_nodes(void);
>   #else
>   static inline unsigned long try_to_compact_pages(gfp_t gfp_mask,
>   			unsigned int order, int alloc_flags,
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 16e1b57..b793922 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1657,7 +1657,7 @@ static void compact_node(int nid)
>   }
>
>   /* Compact all nodes in the system */
> -static void compact_nodes(void)
> +void compact_nodes(void)
>   {
>   	int nid;
>
>

--
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:[~2015-08-07 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 14:03 Pintu Kumar
2015-08-07 14:18 ` Vlastimil Babka [this message]
2015-08-11 10:45   ` PINTU KUMAR

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=55C4BE1A.8050408@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=cpgs@samsung.com \
    --cc=emunson@akamai.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.cz \
    --cc=pintu.k@outlook.com \
    --cc=pintu.k@samsung.com \
    --cc=pintu_agarwal@yahoo.com \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=rohit.kr@samsung.com \
    --cc=vishnu.ps@samsung.com \
    --cc=zhangyanfei@cn.fujitsu.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