From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "pantherchen@versanet.de" <pantherchen@versanet.de>
Cc: Tejun Heo <tj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Boot time regression in 2.6.38 after initial wq merge
Date: Tue, 22 Feb 2011 09:22:54 -0800 [thread overview]
Message-ID: <20110222172254.GA13114@core.coreip.homeip.net> (raw)
In-Reply-To: <4D63D062.3040404@versanet.de>
On Tue, Feb 22, 2011 at 04:04:02PM +0100, pantherchen@versanet.de wrote:
> On 02/22/2011 10:15 AM, Dmitry Torokhov wrote:
> >I'd like to see rc6 tried.
>
> Unfortunately it shows the same behavior [0]. (To speed things up, I
> used a stripped down kernel config [1], while the first two posted
> boot charts used Ubuntu's stock kernels.)
>
> I was surprised that the kernel directly built from the wq branch
> and the last "good" kernel from Linus' tree with the 33 patches
> applied don't show the increased boot time - shouldn't they all be
> the same?
>
No, because there were more merges between your last-known-good (which
is somewhere in the middle of Jiri's HID merge) and Tejun's workqueue
pull. Namely there was merge of my tree that changed serio from using
kseriod to the common workqueue.
Just to confirm, if you revert commit
8ee294cd9def0004887da7f44b80563493b0a097
from 2.6.38-rc6, does this restore boot time?
--
Dmitry
next prev parent reply other threads:[~2011-02-22 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D62CE9C.7090806@versanet.de>
2011-02-22 8:17 ` Tejun Heo
2011-02-22 8:52 ` Dmitry Torokhov
2011-02-22 9:02 ` Tejun Heo
2011-02-22 9:15 ` Dmitry Torokhov
2011-02-22 15:04 ` pantherchen
2011-02-22 17:22 ` Dmitry Torokhov [this message]
2011-02-22 17:59 ` Dmitry Torokhov
2011-02-22 19:32 ` pantherchen
2011-02-22 19:52 ` Dmitry Torokhov
2011-02-22 20:14 ` pantherchen
2011-02-23 5:20 ` Dmitry Torokhov
2011-02-23 9:38 ` Tejun Heo
2011-02-23 10:22 ` Dmitry Torokhov
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=20110222172254.GA13114@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantherchen@versanet.de \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®