lkml.org 
[lkml]   [2016]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/5] Reduce memory waste by page extension user
Date
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>

This patchset tries to reduce memory waste by page extension user.

First case is architecture supported debug_pagealloc. It doesn't
requires additional memory if guard page isn't used. 8 bytes per
page will be saved in this case.

Second case is related to page owner feature. Until now, if page_ext
users want to use it's own fields on page_ext, fields should be
defined in struct page_ext by hard-coding. It has a following problem.

struct page_ext {
#ifdef CONFIG_A
int a;
#endif
#ifdef CONFIG_B
int b;
#endif
};

Assume that kernel is built with both CONFIG_A and CONFIG_B.
Even if we enable feature A and doesn't enable feature B at runtime,
each entry of struct page_ext takes two int rather than one int.
It's undesirable waste so this patch tries to reduce it. By this patchset,
we can save 20 bytes per page dedicated for page owner feature
in some configurations.

Thanks.

Joonsoo Kim (5):
mm/debug_pagealloc: clean-up guard page handling code
mm/debug_pagealloc: don't allocate page_ext if we don't use guard page
mm/page_owner: move page_owner specific function to page_owner.c
mm/page_ext: support extra space allocation by page_ext user
mm/page_owner: don't define fields on struct page_ext by hard-coding

include/linux/page_ext.h | 8 +--
include/linux/page_owner.h | 2 +
mm/page_alloc.c | 44 +++++++------
mm/page_ext.c | 41 +++++++++---
mm/page_owner.c | 152 ++++++++++++++++++++++++++++++++++++++-------
mm/vmstat.c | 79 -----------------------
6 files changed, 190 insertions(+), 136 deletions(-)

--
1.9.1

\
 
 \ /
  Last update: 2016-08-11 01:01    [W:0.085 / U:4.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site