LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sergei Rogachev <rogachevsergei@gmail.com>
To: akpm@linux-foundation.org, iamjoonsoo.kim@lge.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Sergei Rogachev <rogachevsergei@gmail.com>
Subject: [PATCH 0/1] mm/page_ext: remove unnecessary stack_trace field
Date: Tue, 27 Jan 2015 00:52:11 +0300	[thread overview]
Message-ID: <1422309132-28030-1-git-send-email-rogachevsergei@gmail.com> (raw)

The functionality named "page owner" has resurrected the structure page_ext
which is used for keeping additional page-related information. Every page in
the system has its own corresponding page_ext structure.

Page owner uses this structure to keep allocation order, gfp_mask and backtrace
entries; moreover page_ext includes a field of type "struct stack_trace". And
this field is used for collecting backtraces: a pointer to struct stack_trace is
passed to save_stack_trace in the function __set_page_owner. But it is really
not necessary to keep dedicated stack_trace structures for all physical pages in
the system, only an amount of saved backtrace entries is needed to be saved.

The stack_trace structure can be allocated on the stack (it is relatively small)
and used for save_stack_trace invocation. Such change can save 12 bytes of
memory per page if page owner functionality is enabled.

Sergei Rogachev (1):
  mm/page_ext: remove unnecessary stack_trace field

 include/linux/page_ext.h |  2 +-
 mm/page_owner.c          | 21 ++++++++++++---------
 2 files changed, 13 insertions(+), 10 deletions(-)

-- 
1.9.1


             reply	other threads:[~2015-01-26 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 21:52 Sergei Rogachev [this message]
2015-01-26 21:52 ` [PATCH 1/1] " Sergei Rogachev
2015-01-27  8:36   ` Joonsoo Kim
2015-01-27 22:43   ` Andrew Morton
2015-01-28 19:08     ` Sergei Rogachev

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=1422309132-28030-1-git-send-email-rogachevsergei@gmail.com \
    --to=rogachevsergei@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH 0/1] mm/page_ext: remove unnecessary stack_trace field' \
    /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

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