lkml.org 
[lkml]   [2015]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCHv4 18/24] thp, mm: split_huge_page(): caller need to lock page
Date
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> writes:

> We're going to use migration entries instead of compound_lock() to
> stabilize page refcounts. Setup and remove migration entries require
> page to be locked.
>
> Some of split_huge_page() callers already have the page locked. Let's
> require everybody to lock the page before calling split_huge_page().
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>

Why not have split_huge_page_locked/unlocked, and call the one which
takes lock internally every where ?

-aneesh



\
 
 \ /
  Last update: 2015-03-30 16:41    [W:0.262 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site