From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752837AbbJRF72 (ORCPT ); Sun, 18 Oct 2015 01:59:28 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:46028 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751872AbbJRF71 (ORCPT ); Sun, 18 Oct 2015 01:59:27 -0400 Date: Sat, 17 Oct 2015 22:59:26 -0700 From: Greg Kroah-Hartman To: Alexander Holler Cc: 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: <20151018055926.GB31909@kroah.com> References: <5622956F.80408@ahsoftware.de> <56229B0B.80100@ahsoftware.de> <56229E1A.8010803@ahsoftware.de> <20151017193606.GA2315@kroah.com> <5623272A.1050205@ahsoftware.de> <20151018051443.GA29830@kroah.com> <56232C22.4030502@ahsoftware.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56232C22.4030502@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 Sun, Oct 18, 2015 at 07:20:34AM +0200, Alexander Holler wrote: > Am 18.10.2015 um 07:14 schrieb Greg Kroah-Hartman: > >On Sun, Oct 18, 2015 at 06:59:22AM +0200, Alexander Holler wrote: > >>Am 17.10.2015 um 21:36 schrieb Greg Kroah-Hartman: > >> > >>>Again, parallelizing does not solve anything, and causes more problems > >>>_and_ makes things take longer. Try it, we have done it in the past and > >>>proven this, it's pretty easy to test :) > >> > >>Just because I'm curious, may I ask how I would test that in the easy way > >>you have in mind? I've just posted the results of my tests (the patch > >>series) but I wonder what you do have in mind. > > > >Use the tool, scripts/bootgraph.pl to create a boot graph of your boot > >sequence. That should show you the drivers, or other areas, that are > >causing your boot to be "slow". > > So I've misunderstood you. I've read your paragraph as that it's easy to > test parallelizing. Ah, ok, if you want to parallelize everything, add some logic in the driver core where the probe() callback is made to spin that off into a new thread for every call, and when it's done, clean up the thread. That's what I did many years ago to try this all out, if you dig in the lkml archives there's probably a patch somewhere that you can base the work off of to test it yourself. hope this helps, greg k-h