From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751662AbbJQSzL (ORCPT ); Sat, 17 Oct 2015 14:55:11 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:37856 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750759AbbJQSzJ (ORCPT ); Sat, 17 Oct 2015 14:55:09 -0400 Date: Sat, 17 Oct 2015 11:55:09 -0700 From: Greg Kroah-Hartman To: Alexander Holler Cc: Linus Torvalds , Linux Kernel Mailing List , Andrew Morton , Russell King , Grant Likely Subject: Re: [PATCH 04/14] init: deps: order network interfaces by link order Message-ID: <20151017185509.GA28601@kroah.com> References: <1445102067-11519-1-git-send-email-holler@ahsoftware.de> <1445102067-11519-5-git-send-email-holler@ahsoftware.de> <5622956F.80408@ahsoftware.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5622956F.80408@ahsoftware.de> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 17, 2015 at 08:37:35PM +0200, Alexander Holler wrote: > I'm making dependencies the only ordering for annotated initcalls. > > Otherwise it's impossible to call initcalls in parallel. We don't ever want to call initcalls in parallel, unless they can properly handle it. All drivers can tell the driver core to use parallel probing if they know they can handle it. See 'enum probe_type' for this. Trying to call initcalls or driver probes in parallel blindly has been proven to both take a longer amount of time, and cause problems for drivers that aren't expecting it. The research on this was done years ago when people were starting to work on booting quicker, and the end result is what we have now where drivers that know they can handle this, can tell the core to let them probe in this manner. The outcome of this work is the sub-second boot time we have today. If your systems are taking longer to boot, then please look into the drivers that are causing this, that is where the real issue is, not in the core of the kernel. thanks, greg k-h