From: Roman Gushchin <guroan@gmail.com>
To: linux-mm@kvack.org
Cc: Matthew Wilcox <willy@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kernel-team@fb.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Roman Gushchin <guro@fb.com>
Subject: [PATCH v2 0/3] vmalloc enhancements
Date: Tue, 12 Feb 2019 09:56:45 -0800 [thread overview]
Message-ID: <20190212175648.28738-1-guro@fb.com> (raw)
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.
v2->v1:
- rebased on top of current mm tree
- switch from atomic to percpu vmalloc page counter
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 | 113 +++++++++++++++++++++++++++-------------
3 files changed, 79 insertions(+), 38 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-12 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 17:56 Roman Gushchin [this message]
2019-02-12 17:56 ` [PATCH v2 1/3] mm: refactor __vunmap() to avoid duplicated call to find_vm_area() Roman Gushchin
2019-02-12 17:56 ` [PATCH v2 2/3] mm: separate memory allocation and actual work in alloc_vmap_area() Roman Gushchin
2019-02-12 17:56 ` [PATCH v2 3/3] mm: show number of vmalloc pages in /proc/meminfo Roman Gushchin
2019-02-12 18:47 ` [PATCH v2 0/3] vmalloc enhancements Johannes Weiner
2019-02-12 20:34 ` Andrew Morton
2019-02-12 22:36 ` Roman Gushchin
2019-02-13 20:26 ` Matthew Wilcox
2019-02-14 0:38 ` Roman Gushchin
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=20190212175648.28738-1-guro@fb.com \
--to=guroan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox