[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86454fa7-6523-70d7-ce36-8c6874d04523@suse.cz>
Date: Wed, 17 Apr 2019 15:36:02 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Roman Gushchin <guro@...com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Matthew Wilcox <willy@...radead.org>,
Johannes Weiner <hannes@...xchg.org>,
Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH 0/3] vmalloc enhancements
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.
Powered by blists - more mailing lists