From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751380AbbCSTmt (ORCPT ); Thu, 19 Mar 2015 15:42:49 -0400 Received: from mail-ig0-f172.google.com ([209.85.213.172]:37889 "EHLO mail-ig0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750782AbbCSTmr (ORCPT ); Thu, 19 Mar 2015 15:42:47 -0400 Date: Thu, 19 Mar 2015 12:42:44 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Eric B Munson cc: Andrew Morton , Vlastimil Babka , Thomas Gleixner , Christoph Lameter , Peter Zijlstra , Mel Gorman , Rik van Riel , Michal Hocko , linux-rt-users@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V6] Allow compaction of unevictable pages In-Reply-To: <1426773430-31052-1-git-send-email-emunson@akamai.com> Message-ID: References: <1426773430-31052-1-git-send-email-emunson@akamai.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 19 Mar 2015, Eric B Munson wrote: > Currently, pages which are marked as unevictable are protected from > compaction, but not from other types of migration. The POSIX real time > extension explicitly states that mlock() will prevent a major page > fault, but the spirit of is is that mlock() should give a process the > ability to control sources of latency, including minor page faults. > However, the mlock manpage only explicitly says that a locked page will > not be written to swap and this can cause some confusion. The > compaction code today, does not give a developer who wants to avoid swap > but wants to have large contiguous areas available any method to achieve > this state. This patch introduces a sysctl for controlling compaction > behavoir with respect to the unevictable lru. Users that demand no page > faults after a page is present can set compact_unevictable to 0 and > users who need the large contiguous areas can enable compaction on > locked memory by leaving the default value of 1. > > To illustrate this problem I wrote a quick test program that mmaps a > large number of 1MB files filled with random data. These maps are > created locked and read only. Then every other mmap is unmapped and I > attempt to allocate huge pages to the static huge page pool. When the > compact_unevictable sysctl is 0, I cannot allocate hugepages after > fragmenting memory. When the value is set to 1, allocations succeed. > > Signed-off-by: Eric B Munson > Cc: Vlastimil Babka > Cc: Thomas Gleixner > Cc: Christoph Lameter > Cc: Peter Zijlstra > Cc: Mel Gorman > Cc: David Rientjes > Cc: Rik van Riel > Cc: Michal Hocko > Cc: linux-rt-users@vger.kernel.org > Cc: linux-mm@kvack.org > Cc: linux-api@vger.kernel.org > Cc: linux-kernel@vger.kernel.org Acked-by: David Rientjes