From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752519AbcEMIFe (ORCPT ); Fri, 13 May 2016 04:05:34 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:35315 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751184AbcEMIFB (ORCPT ); Fri, 13 May 2016 04:05:01 -0400 Date: Fri, 13 May 2016 10:04:58 +0200 From: Michal Hocko To: Sebastian Frias Cc: linux-mm@kvack.org, Andrew Morton , Linus Torvalds , LKML , mason Subject: Re: [PATCH] mm: add config option to select the initial overcommit mode Message-ID: <20160513080458.GF20141@dhcp22.suse.cz> References: <5731CC6E.3080807@laposte.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5731CC6E.3080807@laposte.net> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 10-05-16 13:56:30, Sebastian Frias wrote: [...] > NOTE: I understand that the overcommit mode can be changed dynamically thru > sysctl, but on embedded systems, where we know in advance that overcommit > will be disabled, there's no reason to postpone such setting. To be honest I am not particularly happy about yet another config option. At least not without a strong reason (the one above doesn't sound that way). The config space is really large already. So why a later initialization matters at all? Early userspace shouldn't consume too much address space to blow up later, no? -- Michal Hocko SUSE Labs