From: Vlastimil Babka <vbabka@suse.cz>
To: Roman Gushchin <guro@fb.com>, "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH 0/3] vmalloc enhancements
Date: Wed, 17 Apr 2019 15:36:02 +0200 [thread overview]
Message-ID: <86454fa7-6523-70d7-ce36-8c6874d04523@suse.cz> (raw)
In-Reply-To: <20190329220742.GA5804@tower.DHCP.thefacebook.com>
On 3/29/19 11:07 PM, Roman Gushchin wrote:
>> 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.20.1
>>
>
> Ping. Any comments/suggestions/objections?
I suspect my questions for 3/3 effectively blocked this, so now it
should be unblocked. Haven't checked how this is affected by the
"improve vmap allocation" series, but you were following it closely and
thus should know better.
next prev parent reply other threads:[~2019-04-17 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190225203037.1317-1-guro@fb.com>
2019-02-25 20:30 ` [PATCH 1/3] mm: refactor __vunmap() to avoid duplicated call to find_vm_area() Roman Gushchin
2019-02-28 15:00 ` Vlastimil Babka
2019-02-25 20:30 ` [PATCH 2/3] mm: separate memory allocation and actual work in alloc_vmap_area() Roman Gushchin
2019-03-01 14:43 ` Vlastimil Babka
2019-03-01 16:48 ` Roman Gushchin
2019-04-17 13:27 ` Vlastimil Babka
2019-04-17 19:15 ` Roman Gushchin
2019-02-25 20:30 ` [PATCH 3/3] mm: show number of vmalloc pages in /proc/meminfo Roman Gushchin
2019-03-01 15:05 ` Vlastimil Babka
2019-04-17 13:34 ` Vlastimil Babka
2019-03-29 22:07 ` [PATCH 0/3] vmalloc enhancements Roman Gushchin
2019-04-17 13:36 ` Vlastimil Babka [this message]
2018-12-19 17:37 Roman Gushchin
2019-02-11 19:08 ` Johannes Weiner
2019-02-11 19:18 ` Andrew Morton
2019-02-11 20:46 ` 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=86454fa7-6523-70d7-ce36-8c6874d04523@suse.cz \
--to=vbabka@suse.cz \
--cc=Kernel-team@fb.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--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