From: Vlastimil Babka <vbabka@suse.cz>
To: Ayush Mittal <ayush.m@samsung.com>,
akpm@linux-foundation.org, vinmenon@codeaurora.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: a.sahrawat@samsung.com, pankaj.m@samsung.com, v.narang@samsung.com
Subject: Re: [PATCH 1/1] mm: reducing page_owner structure size
Date: Tue, 10 Oct 2017 11:34:44 +0200 [thread overview]
Message-ID: <31948332-8f98-00c7-4da0-a8d20dacb3ba@suse.cz> (raw)
In-Reply-To: <1507623917-37991-1-git-send-email-ayush.m@samsung.com>
On 10/10/2017 10:25 AM, Ayush Mittal wrote:
> Maximum page order can be at max 10 which can be accomodated
> in short data type(2 bytes).
> last_migrate_reason is defined as enum type whose values can
> be accomodated in short data type (2 bytes).
>
> Total structure size is currently 16 bytes but after changing structure
> size it goes to 12 bytes.
>
> Signed-off-by: Ayush Mittal <ayush.m@samsung.com>
Looks like it works, so why not.
Before:
[ 0.001000] allocated 50331648 bytes of page_ext
After:
[ 0.001000] allocated 41943040 bytes of page_ext
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> mm/page_owner.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_owner.c b/mm/page_owner.c
> index 0fd9dcf..4ab438a 100644
> --- a/mm/page_owner.c
> +++ b/mm/page_owner.c
> @@ -19,9 +19,9 @@
> #define PAGE_OWNER_STACK_DEPTH (16)
>
> struct page_owner {
> - unsigned int order;
> + unsigned short order;
> + short last_migrate_reason;
> gfp_t gfp_mask;
> - int last_migrate_reason;
> depot_stack_handle_t handle;
> };
>
>
--
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>
prev parent reply other threads:[~2017-10-10 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171010082637epcas5p4b5d588057b336b4056b7bd2f84d52b32@epcas5p4.samsung.com>
2017-10-10 8:25 ` Ayush Mittal
2017-10-10 9:34 ` Vlastimil Babka [this message]
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=31948332-8f98-00c7-4da0-a8d20dacb3ba@suse.cz \
--to=vbabka@suse.cz \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=ayush.m@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pankaj.m@samsung.com \
--cc=v.narang@samsung.com \
--cc=vinmenon@codeaurora.org \
/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