[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33d52132-546f-3c8a-3445-cdbc9068589a@suse.cz>
Date: Thu, 27 Sep 2018 14:14:00 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Yang Shi <yang.shi@...ux.alibaba.com>, mhocko@...nel.org,
kirill@...temov.name, willy@...radead.org,
ldufour@...ux.vnet.ibm.com, akpm@...ux-foundation.org
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [v2 PATCH 2/2 -mm] mm: brk: dwongrade mmap_sem to read when
shrinking
On 9/26/18 8:10 PM, Yang Shi wrote:
Again, "downgrade" in the subject
> brk might be used to shinrk memory mapping too other than munmap().
^ shrink
> So, it may hold write mmap_sem for long time when shrinking large
> mapping, as what commit ("mm: mmap: zap pages with read mmap_sem in
> munmap") described.
>
> The brk() will not manipulate vmas anymore after __do_munmap() call for
> the mapping shrink use case. But, it may set mm->brk after
> __do_munmap(), which needs hold write mmap_sem.
>
> However, a simple trick can workaround this by setting mm->brk before
> __do_munmap(). Then restore the original value if __do_munmap() fails.
> With this trick, it is safe to downgrade to read mmap_sem.
>
> So, the same optimization, which downgrades mmap_sem to read for
> zapping pages, is also feasible and reasonable to this case.
>
> The period of holding exclusive mmap_sem for shrinking large mapping
> would be reduced significantly with this optimization.
>
> Cc: Michal Hocko <mhocko@...nel.org>
> Cc: Kirill A. Shutemov <kirill@...temov.name>
> Cc: Matthew Wilcox <willy@...radead.org>
> Cc: Laurent Dufour <ldufour@...ux.vnet.ibm.com>
> Cc: Vlastimil Babka <vbabka@...e.cz>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Yang Shi <yang.shi@...ux.alibaba.com>
Acked-by: Vlastimil Babka <vbabka@...e.cz>
Same nit for the "bool downgrade" name as for patch 1/2.
Thanks,
Vlastimil
Powered by blists - more mailing lists