From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765375AbcLVIbd (ORCPT ); Thu, 22 Dec 2016 03:31:33 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34435 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755826AbcLVIbb (ORCPT ); Thu, 22 Dec 2016 03:31:31 -0500 Date: Thu, 22 Dec 2016 11:31:28 +0300 From: "Kirill A. Shutemov" To: David Rientjes Cc: Andrew Morton , Jonathan Corbet , "Kirill A. Shutemov" , Vlastimil Babka , Mel Gorman , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch] mm, thp: always direct reclaim for MADV_HUGEPAGE even when deferred Message-ID: <20161222083128.GB32480@node.shutemov.name> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 21, 2016 at 04:21:54PM -0800, David Rientjes wrote: > Currently, when defrag is set to "madvise", thp allocations will direct > reclaim. However, when defrag is set to "defer", all thp allocations do > not attempt reclaim regardless of MADV_HUGEPAGE. > > This patch always directly reclaims for MADV_HUGEPAGE regions when defrag > is not set to "never." The idea is that MADV_HUGEPAGE regions really > want to be backed by hugepages and are willing to endure the latency at > fault as it was the default behavior prior to commit 444eb2a449ef ("mm: > thp: set THP defrag by default to madvise and add a stall-free defrag > option"). > > In this form, "defer" is a stronger, more heavyweight version of > "madvise". > > Signed-off-by: David Rientjes Makes senses to me. Acked-by: Kirill A. Shutemov -- Kirill A. Shutemov