Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752643AbdFTU4e (ORCPT ); Tue, 20 Jun 2017 16:56:34 -0400 Received: from mx2.suse.de ([195.135.220.15]:35703 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751920AbdFTU4c (ORCPT ); Tue, 20 Jun 2017 16:56:32 -0400 Date: Tue, 20 Jun 2017 22:56:22 +0200 From: "Luis R. Rodriguez" To: "Luis R. Rodriguez" Cc: akpm@linux-foundation.org, jeyu@redhat.com, shuah@kernel.org, rusty@rustcorp.com.au, ebiederm@xmission.com, dmitry.torokhov@gmail.com, acme@redhat.com, corbet@lwn.net, josh@joshtriplett.org, martin.wilck@suse.com, mmarek@suse.com, pmladek@suse.com, hare@suse.com, rwright@hpe.com, jeffm@suse.com, DSterba@suse.com, fdmanana@suse.com, neilb@suse.com, linux@roeck-us.net, rgoldwyn@suse.com, subashab@codeaurora.org, xypron.glpk@gmx.de, keescook@chromium.org, atomlin@redhat.com, mbenes@suse.cz, paulmck@linux.vnet.ibm.com, dan.j.williams@intel.com, jpoimboe@redhat.com, davem@davemloft.net, mingo@redhat.com, alan@linux.intel.com, tytso@mit.edu, gregkh@linuxfoundation.org, torvalds@linux-foundation.org, linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 0/4] kmod: help make deterministic Message-ID: <20170620205622.GX21846@wotan.suse.de> References: <20170526001630.19203-1-mcgrof@kernel.org> <20170526211228.27764-1-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170526211228.27764-1-mcgrof@kernel.org> 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 Content-Length: 1352 Lines: 30 On Fri, May 26, 2017 at 02:12:24PM -0700, Luis R. Rodriguez wrote: > This v3 nukes the proc sysctl interface in favor for just letting userspace > just check kernel revision. Prior to whenever this is merged userspace should > try to avoid hammering more than 50 kmod threads as they can fail and it'd > get -ENOMEM. > > We do away with the old heuristics on assuming you could end up with > less than max_threads/2 < 50 threads as Dmitry notes this would mean having > a system with 16 MiB of RAM with modules enabled. It simplifies our patch > "kmod: reduce atomic operations on kmod_concurrent" considerbly. > > Since the sysctl interface is gone, this no longer depends on any > other patches, the series is independent. As usual the series is > available on my linux-next 20170526-kmod-only branch which is based > on next-20170526. > > [0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/log/?h=20170526-kmod-only > > Luis > > Luis R. Rodriguez (4): > module: use list_for_each_entry_rcu() on find_module_all() > kmod: reduce atomic operations on kmod_concurrent and simplify > kmod: add test driver to stress test the module loader > kmod: throttle kmod thread limit About a month now with no further nitpicks. What tree should these changes go through if there are no issues? Andrew's, Jessica's ? Luis