From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: guro@fb.com, hannes@cmpxchg.org, vdavydov.dev@gmail.com,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm, memcg: reduce size of struct mem_cgroup by using bit field
Date: Mon, 6 Jan 2020 11:19:47 +0100 [thread overview]
Message-ID: <20200106101947.GD12699@dhcp22.suse.cz> (raw)
In-Reply-To: <1577450633-2098-1-git-send-email-laoar.shao@gmail.com>
On Fri 27-12-19 07:43:52, Yafang Shao wrote:
> There are some members in struct mem_group can be either 0(false) or
> 1(true), so we can define them using bit field to reduce size. With this
> patch, the size of struct mem_cgroup can be reduced by 64 bytes in theory,
> but as there're some MEMCG_PADDING()s, the real number may be different,
> which is relate with the cacheline size. Anyway, this patch could reduce
> the size of struct mem_cgroup more or less.
Pahole says
/* size: 2496, cachelines: 39, members: 48 */
/* sum members: 2364, holes: 8, sum holes: 108 */
/* padding: 24 */
/* forced alignments: 3, forced holes: 2, sum forced holes: 88 */
after the change
/* size: 2496, cachelines: 39, members: 48 */
/* sum members: 2352, holes: 7, sum holes: 108 */
/* sum bitfield members: 6 bits, bit holes: 1, sum bit holes: 26 bits */
/* padding: 32 */
/* forced alignments: 3, forced holes: 2, sum forced holes: 88 */
so exactly 0 change. I do not think this reshuffling is worth it.
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Cc: Roman Gushchin <guro@fb.com>
> ---
> include/linux/memcontrol.h | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> index a7a0a1a5..f68a9ef 100644
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -229,20 +229,26 @@ struct mem_cgroup {
> /*
> * Should the accounting and control be hierarchical, per subtree?
> */
> - bool use_hierarchy;
> + unsigned int use_hierarchy : 1;
> +
> + /* Legacy tcp memory accounting */
> + unsigned int tcpmem_active : 1;
> + unsigned int tcpmem_pressure : 1;
>
> /*
> * Should the OOM killer kill all belonging tasks, had it kill one?
> */
> - bool oom_group;
> + unsigned int oom_group : 1;
>
> /* protected by memcg_oom_lock */
> - bool oom_lock;
> - int under_oom;
> + unsigned int oom_lock : 1;
>
> - int swappiness;
> /* OOM-Killer disable */
> - int oom_kill_disable;
> + unsigned int oom_kill_disable : 1;
> +
> + int under_oom;
> +
> + int swappiness;
>
> /* memory.events and memory.events.local */
> struct cgroup_file events_file;
> @@ -297,9 +303,6 @@ struct mem_cgroup {
>
> unsigned long socket_pressure;
>
> - /* Legacy tcp memory accounting */
> - bool tcpmem_active;
> - int tcpmem_pressure;
>
> #ifdef CONFIG_MEMCG_KMEM
> /* Index in the kmem_cache->memcg_params.memcg_caches array */
> --
> 1.8.3.1
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2020-01-06 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 12:43 Yafang Shao
2019-12-27 12:43 ` [PATCH] mm, memcg: reset memcg's memory.{min, low} for reclaiming itself Yafang Shao
2019-12-27 23:49 ` Roman Gushchin
2019-12-28 1:45 ` Yafang Shao
2019-12-28 2:59 ` Roman Gushchin
2019-12-28 4:24 ` Yafang Shao
2019-12-27 23:55 ` [PATCH] mm, memcg: reduce size of struct mem_cgroup by using bit field Roman Gushchin
2019-12-28 4:22 ` Yafang Shao
2019-12-31 22:31 ` Andrew Morton
2020-01-02 5:43 ` Yafang Shao
2020-01-06 10:19 ` Michal Hocko [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=20200106101947.GD12699@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.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