Re: [PATCH 0/3] vmalloc enhancements

2019-04-17 Thread Vlastimil Babka
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 |

Re: [PATCH 0/3] vmalloc enhancements

2019-03-29 Thread Roman Gushchin
On Mon, Feb 25, 2019 at 12:30:34PM -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

Re: [PATCH 0/3] vmalloc enhancements

2019-02-11 Thread Roman Gushchin
On Mon, Feb 11, 2019 at 11:18:45AM -0800, Andrew Morton wrote: > On Mon, 11 Feb 2019 14:08:22 -0500 Johannes Weiner wrote: > > > 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

Re: [PATCH 0/3] vmalloc enhancements

2019-02-11 Thread Andrew Morton
On Mon, 11 Feb 2019 14:08:22 -0500 Johannes Weiner wrote: > 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 pag

Re: [PATCH 0/3] vmalloc enhancements

2019-02-11 Thread Johannes Weiner
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