From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754392AbbFKMa3 (ORCPT ); Thu, 11 Jun 2015 08:30:29 -0400 Received: from cantor2.suse.de ([195.135.220.15]:44608 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752839AbbFKMaY (ORCPT ); Thu, 11 Jun 2015 08:30:24 -0400 Message-ID: <55797F57.8040001@suse.cz> Date: Thu, 11 Jun 2015 14:30:15 +0200 From: Vlastimil Babka User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "Kirill A. Shutemov" , Andrew Morton , Andrea Arcangeli , Hugh Dickins CC: Dave Hansen , Mel Gorman , Rik van Riel , Christoph Lameter , Naoya Horiguchi , Steve Capper , "Aneesh Kumar K.V" , Johannes Weiner , Michal Hocko , Jerome Marchand , Sasha Levin , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCHv6 36/36] thp: update documentation References: <1433351167-125878-1-git-send-email-kirill.shutemov@linux.intel.com> <1433351167-125878-37-git-send-email-kirill.shutemov@linux.intel.com> In-Reply-To: <1433351167-125878-37-git-send-email-kirill.shutemov@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/03/2015 07:06 PM, Kirill A. Shutemov wrote: > The patch updates Documentation/vm/transhuge.txt to reflect changes in > THP design. One thing I'm missing is info about the deferred splitting. > Signed-off-by: Kirill A. Shutemov > --- > Documentation/vm/transhuge.txt | 124 +++++++++++++++++++++++------------------ > 1 file changed, 69 insertions(+), 55 deletions(-) > > diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt > index 6b31cfbe2a9a..2352b12cae93 100644 > --- a/Documentation/vm/transhuge.txt > +++ b/Documentation/vm/transhuge.txt > @@ -35,10 +35,10 @@ miss is going to run faster. > > == Design == > > -- "graceful fallback": mm components which don't have transparent > - hugepage knowledge fall back to breaking a transparent hugepage and > - working on the regular pages and their respective regular pmd/pte > - mappings > +- "graceful fallback": mm components which don't have transparent hugepage > + knowledge fall back to breaking huge pmd mapping into table of ptes and, > + if nesessary, split a transparent hugepage. Therefore these components necessary > + > +split_huge_page uses migration entries to stabilize page->_count and > +page->_mapcount. Hm, what if there's some physical memory scanner taking page->_count pins? I think compaction shouldn't be an issue, but maybe some others?