All of lore.kernel.org
 help / color / mirror / Atom feed
From: js1304@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@kernel.org>,
	linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
	David Rientjes <rientjes@google.com>,
	Mel Gorman <mgorman@suse.de>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: [RFC PATCH 0/5] pro-active compaction
Date: Fri, 13 Jan 2017 16:14:28 +0900	[thread overview]
Message-ID: <1484291673-2239-1-git-send-email-iamjoonsoo.kim@lge.com> (raw)

From: Joonsoo Kim <iamjoonsoo.kim@lge.com>

Hello,

This is a patchset for pro-active compaction to reduce fragmentation.
It is a just RFC patchset so implementation detail isn't good.
I submit this for people who want to check the effect of pro-active
compaction.

Patch 1 ~ 4 introduces new metric for checking fragmentation. I think
that this new metric is useful to check fragmentation state
regardless of usefulness of pro-active compaction. Please let me know
if someone see that this new metric is useful. I'd like to submit it,
separately.
	
Any feedback is more than welcome.

Thanks.

Joonsoo Kim (5):
  mm/vmstat: retrieve suitable free pageblock information just once
  mm/vmstat: rename variables/functions about buddyinfo
  mm: introduce exponential moving average to unusable free index
  mm/vmstat: introduce /proc/fraginfo to get fragmentation stat stably
  mm/compaction: run the compaction whenever fragmentation ratio exceeds
    the threshold

 include/linux/mmzone.h |   3 +
 mm/compaction.c        | 280 +++++++++++++++++++++++++++++++++++++++++++++++--
 mm/internal.h          |  21 ++++
 mm/page_alloc.c        |  33 ++++++
 mm/vmstat.c            | 101 ++++++++++++------
 5 files changed, 397 insertions(+), 41 deletions(-)

-- 
1.9.1

--
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:[~2017-01-13  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  7:14 js1304 [this message]
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
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=1484291673-2239-1-git-send-email-iamjoonsoo.kim@lge.com \
    --to=js1304@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    --cc=rientjes@google.com \
    --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.