From: Vlastimil Babka <vbabka@suse.cz>
To: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [RFC PATCH 1/5] mm/vmstat: retrieve suitable free pageblock information just once
Date: Thu, 19 Jan 2017 11:47:09 +0100 [thread overview]
Message-ID: <123434e3-1d63-6ba7-1bdb-7bb66b4619a6@suse.cz> (raw)
In-Reply-To: <1484291673-2239-2-git-send-email-iamjoonsoo.kim@lge.com>
On 01/13/2017 08:14 AM, js1304@gmail.com wrote:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> It's inefficient to retrieve buddy information for fragmentation index
> calculation on every order. By using some stack memory, we could retrieve
> it once and reuse it to compute all the required values. MAX_ORDER is
> usually small enough so there is no big risk about stack overflow.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Sounds useful regardless of the rest of the series.
Acked-by: Vlastimil Babka <vbabka@suse.cz>
A nit below.
> ---
> mm/vmstat.c | 25 ++++++++++++-------------
> 1 file changed, 12 insertions(+), 13 deletions(-)
>
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 7c28df3..e1ca5eb 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -821,7 +821,7 @@ unsigned long node_page_state(struct pglist_data *pgdat,
> struct contig_page_info {
> unsigned long free_pages;
> unsigned long free_blocks_total;
> - unsigned long free_blocks_suitable;
> + unsigned long free_blocks_order[MAX_ORDER];
No need to rename _suitable to _order IMHO. The meaning is still the
same, it's just an array now. For me a name "free_blocks_order" would
suggest it's just simple zone->free_area[order].nr_free.
--
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>
next prev parent reply other threads:[~2017-01-19 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 7:14 [RFC PATCH 0/5] pro-active compaction js1304
2017-01-13 7:14 ` [RFC PATCH 1/5] mm/vmstat: retrieve suitable free pageblock information just once js1304
2017-01-19 10:47 ` Vlastimil Babka [this message]
2017-01-23 3:17 ` Joonsoo Kim
2017-01-19 11:51 ` Michal Hocko
2017-01-19 12:06 ` Vlastimil Babka
2017-01-13 7:14 ` [RFC PATCH 2/5] mm/vmstat: rename variables/functions about buddyinfo js1304
2017-01-13 7:14 ` [RFC PATCH 3/5] mm: introduce exponential moving average to unusable free index js1304
2017-01-19 12:52 ` Vlastimil Babka
2017-01-23 5:27 ` Joonsoo Kim
2017-01-13 7:14 ` [RFC PATCH 4/5] mm/vmstat: introduce /proc/fraginfo to get fragmentation stat stably js1304
2017-01-13 7:14 ` [RFC PATCH 5/5] mm/compaction: run the compaction whenever fragmentation ratio exceeds the threshold js1304
2017-01-19 13:39 ` Vlastimil Babka
2017-01-13 9:24 ` [RFC PATCH 0/5] pro-active compaction Michal Hocko
2017-01-17 0:48 ` Joonsoo 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=123434e3-1d63-6ba7-1bdb-7bb66b4619a6@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=rientjes@google.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