Re: [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore

On 04/07/22 at 03:36pm, Chris Down wrote: > Omar Sandoval writes: > > From: Omar Sandoval > > > > Commit 3ee48b6af49c ("mm, x86: Saving vmcore with non-lazy freeing of > > vmas") introduced set_iounmap_nonlazy(), which sets vmap_lazy_nr to > > lazy_max_pages() + 1, ensuring that any future vunmap

RE: [PATCH 2/2] makedumpfile: break loop after last dumpable page

-Original Message- > Hi Kazu, > > On Thu, 7 Apr 2022 06:43:00 + > HAGIO KAZUHITO(萩尾　一仁) wrote: > > > -Original Message- > > > Once the last dumpable page was processed there is no need to finish the > > > loop to the last page. Thus exit early to improve performance. > > > >

Re: [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore

Omar Sandoval writes: From: Omar Sandoval Commit 3ee48b6af49c ("mm, x86: Saving vmcore with non-lazy freeing of vmas") introduced set_iounmap_nonlazy(), which sets vmap_lazy_nr to lazy_max_pages() + 1, ensuring that any future vunmaps() immediately purge the vmap areas instead of doing it lazil

Re: [PATCH 2/2] makedumpfile: break loop after last dumpable page

Hi Kazu, On Thu, 7 Apr 2022 06:43:00 + HAGIO KAZUHITO(萩尾　一仁) wrote: > -Original Message- > > Once the last dumpable page was processed there is no need to finish the > > loop to the last page. Thus exit early to improve performance. > > > > Signed-off-by: Philipp Rudo > > --- > >

Re: [PATCH v2] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore

> From: Omar Sandoval > > Commit 3ee48b6af49c ("mm, x86: Saving vmcore with non-lazy freeing of > vmas") introduced set_iounmap_nonlazy(), which sets vmap_lazy_nr to > lazy_max_pages() + 1, ensuring that any future vunmaps() immediately > purge the vmap areas instead of doing it lazily. > > Comm