[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190211190822.GA14443@cmpxchg.org>
Date: Mon, 11 Feb 2019 14:08:22 -0500
From: Johannes Weiner <hannes@...xchg.org>
To: Roman Gushchin <guroan@...il.com>
Cc: linux-mm@...ck.org, Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>, linux-kernel@...r.kernel.org,
kernel-team@...com, Roman Gushchin <guro@...com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/3] vmalloc enhancements
These slipped through the cracks. +CC Andrew directly.
Andrew, if it's not too late yet, could you consider them for 5.1?
On Wed, Dec 19, 2018 at 09:37:48AM -0800, Roman Gushchin wrote:
> The patchset contains few changes to the vmalloc code, which are
> leading to some performance gains and code simplification.
>
> Also, it exports a number of pages, used by vmalloc(),
> in /proc/meminfo.
>
> Patch (1) removes some redundancy on __vunmap().
> Patch (2) separates memory allocation and data initialization
> in alloc_vmap_area()
> Patch (3) adds vmalloc counter to /proc/meminfo.
>
> RFC->v1:
> - removed bogus empty lines (suggested by Matthew Wilcox)
> - made nr_vmalloc_pages static (suggested by Matthew Wilcox)
> - dropped patch 3 from RFC patchset, will post later with
> some other changes
> - dropped RFC
>
> Roman Gushchin (3):
> mm: refactor __vunmap() to avoid duplicated call to find_vm_area()
> mm: separate memory allocation and actual work in alloc_vmap_area()
> mm: show number of vmalloc pages in /proc/meminfo
>
> fs/proc/meminfo.c | 2 +-
> include/linux/vmalloc.h | 2 +
> mm/vmalloc.c | 107 ++++++++++++++++++++++++++--------------
> 3 files changed, 73 insertions(+), 38 deletions(-)
>
> --
> 2.19.2
>
Powered by blists - more mailing lists