From: Greg KH <gregkh@suse.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Simon Glass <sjg@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org,
Sarah Sharp <sarah.a.sharp@linux.intel.com>
Subject: Re: [PATCH] usb: Use a workqueue in usb_add_hcd() to reduce boot time
Date: Tue, 24 Jan 2012 09:22:31 -0800 [thread overview]
Message-ID: <20120124172231.GA27273@suse.de> (raw)
In-Reply-To: <20120124165711.GC3836@linutronix.de>
On Tue, Jan 24, 2012 at 05:57:11PM +0100, Sebastian Andrzej Siewior wrote:
> * Alan Stern | 2012-01-21 11:11:09 [-0500]:
>
> >Doing time-consuming things later won't make any difference. That is,
> >suppose the boot sequence performs activities A and B, where A takes a
> >long time. Doing A later, so that the boot sequence performs B and
> >then A, won't change the total time required.
>
> That is true. However if you show the gui _now_ and look for USB later
> then it feels faster and this is usually enough.
Which has been done before, with great success (i.e. we did it for
Moblin boot times), so it shouldn't be that big of an issue.
Which points out the question, exactly what is the issue here? We have
"multithreaded" pci driver startup for a long time now, did that stop
working here? If you use bootchart, does it show that the USB host
driver is stoping the machine from proceeding to the next stage in the
boot process?
>From my experience, I never saw the USB host controller get in the way
at all, it was always somethine else happening that caused problems
(i.e. video.)
Simon, do you have boot charts anywhere showing this?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-24 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 23:37 [PATCH] usb: Use a workqueue in usb_add_hcd() to reduce boot time Simon Glass
2012-01-20 15:46 ` Alan Stern
2012-01-20 23:47 ` Simon Glass
2012-01-21 16:11 ` Alan Stern
2012-01-24 16:57 ` Sebastian Andrzej Siewior
2012-01-24 17:22 ` Greg KH [this message]
2012-01-26 23:48 ` Simon Glass
2012-01-26 23:51 ` Greg KH
2012-01-26 23:57 ` Simon Glass
2012-01-27 0:07 ` Greg KH
2012-01-27 2:45 ` Simon Glass
2012-01-23 16:14 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120124172231.GA27273@suse.de \
--to=gregkh@suse.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=sjg@chromium.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).