All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Henk Martijn <h.h.martijn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [bisected] boot speed regression in current git
Date: Fri, 07 Aug 2009 12:27:40 +0200	[thread overview]
Message-ID: <4A7C019C.4090003@gmail.com> (raw)
In-Reply-To: <4A7BFCC4.8060006@gmail.com>

Henk Martijn a écrit :
> hi,
> 
> in current git my booting takes > 20 s longer. 
> 
> I bisected this to "net: restore the original spinlock to protect unicast list" commit: a6ac65db2329e7685299666f5f7b6093c7b0f3a0
> reverting this commit gives me back 20 s in boot time. 
> 
> I've attached the two dmesg logs. 
> 
> I can help with testing if necessary. 
> 
> Regards,
> 
> Henk 

Could you try Ingo fix ?

http://git2.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=0bf52b981770cbf006323bab5177f2858a196766

Should be pulled soon

  reply	other threads:[~2009-08-07 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 10:07 [bisected] boot speed regression in current git Henk Martijn
2009-08-07 10:27 ` Eric Dumazet [this message]
2009-08-07 10:54 ` Frans Pop
2009-08-07 11:27   ` Henk Martijn

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=4A7C019C.4090003@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=h.h.martijn@gmail.com \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.