[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190701092037.GL6376@dhcp22.suse.cz>
Date: Mon, 1 Jul 2019 11:20:37 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Pengfei Li <lpf.vector@...il.com>
Cc: akpm@...ux-foundation.org, peterz@...radead.org, urezki@...il.com,
rpenyaev@...e.de, guro@...com, aryabinin@...tuozzo.com,
rppt@...ux.ibm.com, mingo@...nel.org, rick.p.edgecombe@...el.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] mm/vmalloc.c: improve readability and rewrite
vmap_area
On Sun 30-06-19 15:56:45, Pengfei Li wrote:
> Hi,
>
> This series of patches is to reduce the size of struct vmap_area.
>
> Since the members of struct vmap_area are not being used at the same time,
> it is possible to reduce its size by placing several members that are not
> used at the same time in a union.
>
> The first 4 patches did some preparatory work for this and improved
> readability.
>
> The fifth patch is the main patch, it did the work of rewriting vmap_area.
>
> More details can be obtained from the commit message.
None of the commit messages talk about the motivation. Why do we want to
add quite some code to achieve this? How much do we save? This all
should be a part of the cover letter.
> Thanks,
>
> Pengfei
>
> Pengfei Li (5):
> mm/vmalloc.c: Introduce a wrapper function of insert_vmap_area()
> mm/vmalloc.c: Introduce a wrapper function of
> insert_vmap_area_augment()
> mm/vmalloc.c: Rename function __find_vmap_area() for readability
> mm/vmalloc.c: Modify function merge_or_add_vmap_area() for readability
> mm/vmalloc.c: Rewrite struct vmap_area to reduce its size
>
> include/linux/vmalloc.h | 28 +++++---
> mm/vmalloc.c | 144 +++++++++++++++++++++++++++-------------
> 2 files changed, 117 insertions(+), 55 deletions(-)
>
> --
> 2.21.0
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists