From: Johannes Weiner <hannes@cmpxchg.org>
To: Roman Gushchin <guroan@gmail.com>
Cc: linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Roman Gushchin <guro@fb.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] vmalloc enhancements
Date: Mon, 11 Feb 2019 14:08:22 -0500 [thread overview]
Message-ID: <20190211190822.GA14443@cmpxchg.org> (raw)
In-Reply-To: <20181219173751.28056-1-guro@fb.com>
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
>
next prev parent reply other threads:[~2019-02-11 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 17:37 [PATCH 0/3] vmalloc enhancements Roman Gushchin
2018-12-19 17:37 ` [PATCH 1/3] mm: refactor __vunmap() to avoid duplicated call to find_vm_area() Roman Gushchin
2018-12-19 17:37 ` [PATCH 2/3] mm: separate memory allocation and actual work in alloc_vmap_area() Roman Gushchin
2018-12-19 17:37 ` [PATCH 3/3] mm: show number of vmalloc pages in /proc/meminfo Roman Gushchin
2019-02-11 19:08 ` Johannes Weiner [this message]
2019-02-11 19:18 ` [PATCH 0/3] vmalloc enhancements Andrew Morton
2019-02-11 20:46 ` Roman Gushchin
2019-02-25 20:30 Roman Gushchin
2019-03-29 22:07 ` Roman Gushchin
2019-04-17 13:36 ` Vlastimil Babka
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=20190211190822.GA14443@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=guroan@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.