Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753488AbbBYStU (ORCPT ); Wed, 25 Feb 2015 13:49:20 -0500 Received: from mout.gmx.net ([212.227.17.21]:57481 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752883AbbBYStR (ORCPT ); Wed, 25 Feb 2015 13:49:17 -0500 Message-ID: <54EE18DF.2040201@gmx.de> Date: Wed, 25 Feb 2015 19:47:59 +0100 From: Heinrich Schuchardt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: David Rientjes CC: Andrew Morton , Aaron Tomlin , Andy Lutomirski , Davidlohr Bueso , "David S. Miller" , Fabian Frederick , Guenter Roeck , "H. Peter Anvin" , Ingo Molnar , Jens Axboe , Joe Perches , Johannes Weiner , Kees Cook , Michael Marineau , Oleg Nesterov , "Paul E. McKenney" , Peter Zijlstra , Prarit Bhargava , Rik van Riel , Rusty Russell , Steven Rostedt , Thomas Gleixner , Vladimir Davydov , linux-kernel@vger.kernel.org, Jonathan Corbet Subject: Re: [PATCH 3/3] kernel/sysctl.c: threads-max observe limits References: <1424722477-23758-1-git-send-email-xypron.glpk@gmx.de> <1424806701-30099-1-git-send-email-xypron.glpk@gmx.de> <1424806701-30099-4-git-send-email-xypron.glpk@gmx.de> <54ECED97.5070500@gmx.de> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:GQobcoaoaR5kTrq3zEQoaTos8OGVdFoQwko6sI/JkLH+IOAZaN8 TdWembdfzZFr54HkIdWr1IE1h6+4zssLWZbQUbcGqEHiAijLCIIx+NFhnaNX8Qo+Grg+XOq Fnb9oNI51UeI+tocmS7iHVSohb9v8QBmliRDu9B2Rj1+DcBX3t6daOzrU1UFHKjrj8Wh0uF 2wOYpcWiyxzmSHi+cu0xA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1562 Lines: 41 On 24.02.2015 23:20, David Rientjes wrote: > On Tue, 24 Feb 2015, Heinrich Schuchardt wrote: > >>>> Users can change the maximum number of threads by writing to >>>> /proc/sys/kernel/threads-max. >>>> >>>> With the patch the value entered is checked against the same >>>> limits that apply when fork_init is called. >>>> >>> >>> Correct me if I'm wrong, but this is a change in functionality (without >>> update to Documentation/sysctl/kernel.txt which describes threads-max) >>> since it does not allow the value to be lowered as before from the >>> calculation involving totalram_pages. The value passed to >>> set_max_threads() only caps the value. >> >> threads_max is set to the value the user inputs if it is inside the >> interval [20, FUTEX_TID_MASK] and it is capped by the value calculated >> from totalram_pages. >> >> So lowering and raising is still possible (inside the limits). >> > > I believe this information should be added to the documentation cited > above which mentions threads-max since users will otherwise be unfamiliar > with the limits imposed. Hello David, I guess the documentation fix should be put into a separate patch (of the same patch series) as Jonathan Corbet uses a separate git tree to consolidate documentation changes. Is that ok with you? Best regards Heinrich -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/