From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932100Ab1JKTy2 (ORCPT ); Tue, 11 Oct 2011 15:54:28 -0400 Received: from mail-qy0-f174.google.com ([209.85.216.174]:34408 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932065Ab1JKTy0 (ORCPT ); Tue, 11 Oct 2011 15:54:26 -0400 Date: Tue, 11 Oct 2011 12:54:19 -0700 From: Andrew Morton To: Satoru Moriya Cc: David Rientjes , Rik van Riel , Randy Dunlap , Satoru Moriya , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "lwoodman@redhat.com" , Seiji Aguchi , "hughd@google.com" , "hannes@cmpxchg.org" Subject: Re: [PATCH -v2 -mm] add extra free kbytes tunable Message-Id: <20111011125419.2702b5dc.akpm@linux-foundation.org> In-Reply-To: <65795E11DBF1E645A09CEC7EAEE94B9CB516CBC4@USINDEVS02.corp.hds.com> References: <20110901105208.3849a8ff@annuminas.surriel.com> <20110901100650.6d884589.rdunlap@xenotime.net> <20110901152650.7a63cb8b@annuminas.surriel.com> <20111010153723.6397924f.akpm@linux-foundation.org> <65795E11DBF1E645A09CEC7EAEE94B9CB516CBC4@USINDEVS02.corp.hds.com> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 11 Oct 2011 15:32:11 -0400 Satoru Moriya wrote: > On 10/10/2011 06:37 PM, Andrew Morton wrote: > > On Fri, 7 Oct 2011 20:08:19 -0700 (PDT) David Rientjes > > wrote: > > > >> On Thu, 1 Sep 2011, Rik van Riel wrote: > > > > The page allocator already tries harder if the caller has > > rt_task(current). Why is this inadequate? Can we extend this idea > > further to fix whatever-the-problem-is? > > Actually page allocator decreases min watermark to 3/4 * min watermark > for rt-task. But in our case some applications create a lot of > processes and if all of them are rt-task, the amount of watermark > bonus(1/4 * min watermark) is not enough. > > If we can tune the amount of bonus, it may be fine. But that is > almost all same as extra free kbytes. This situation is detectable at runtime. If realtime tasks are being stalled in the page allocator then start to increase the free-page reserves. A little control system.