From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752843Ab1LUCbT (ORCPT ); Tue, 20 Dec 2011 21:31:19 -0500 Received: from db3ehsobe003.messaging.microsoft.com ([213.199.154.141]:33101 "EHLO DB3EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751601Ab1LUCbQ (ORCPT ); Tue, 20 Dec 2011 21:31:16 -0500 X-SpamScore: -10 X-BigFish: VPS-10(zzbb2dI1432N98dKzz1202hzzz2fh668h839h93fh) X-Forefront-Antispam-Report: CIP:160.33.98.74;KIP:(null);UIP:(null);IPV:NLI;H:mail7.fw-bc.sony.com;RD:mail7.fw-bc.sony.com;EFVD:NLI Message-ID: <4EF144D1.2020807@am.sony.com> Date: Tue, 20 Dec 2011 18:30:41 -0800 From: Frank Rowand Reply-To: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Thunderbird/3.1.10 MIME-Version: 1.0 To: Anton Vorontsov CC: "Rowand, Frank" , David Rientjes , KOSAKI Motohiro , Michal Hocko , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Rik van Riel , Pavel Machek , Greg Kroah-Hartman , Andrew Morton , John Stultz , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Johannes Weiner , KAMEZAWA Hiroyuki , Alan Cox , "tbird20d@gmail.com" Subject: Re: Android low memory killer vs. memory pressure notifications References: <20111219025328.GA26249@oksana.dev.rtsoft.ru> <20111219121255.GA2086@tiehlicka.suse.cz> <20111220145654.GA26881@oksana.dev.rtsoft.ru> <20111221002853.GA11504@oksana.dev.rtsoft.ru> <4EF132EA.7000300@am.sony.com> <20111221020723.GA5214@oksana.dev.rtsoft.ru> In-Reply-To: <20111221020723.GA5214@oksana.dev.rtsoft.ru> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-OriginatorOrg: am.sony.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/20/11 18:07, Anton Vorontsov wrote: > On Tue, Dec 20, 2011 at 05:14:18PM -0800, Frank Rowand wrote: < snip > >> And for embedded and for real-time, some of us do not want cgroups to be >> a mandatory thing. We want it to remain configurable. My personal >> interest is in keeping the latency of certain critical paths (especially >> in the scheduler) short and consistent. > > Much thanks for your input! That would be quite strong argument for going > with /dev/mem_notify approach. Do you have any specific numbers how cgroups > makes scheduler latencies worse? Sorry, I don't have specific numbers. And the numbers would be workload specific anyway. -Frank