From: Andrew Morton <akpm@linux-foundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: linkwatch bustage in git-net
Date: Tue, 8 May 2007 22:20:33 -0700 [thread overview]
Message-ID: <20070508222033.4e57a580.akpm@linux-foundation.org> (raw)
My Vaio is taking 5-10x longer to boot when git-net as of five minutes ago
is applied.
It's not very clear what's gone wrong. A few linkwatch things are showing
up in profiles, but it's not burning excessive CPU afaict.
next reply other threads:[~2007-05-09 5:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:20 Andrew Morton [this message]
2007-05-09 5:31 ` linkwatch bustage in git-net Herbert Xu
2007-05-09 5:45 ` Herbert Xu
[not found] ` <20070508225153.d538f79c.akpm@linux-foundation.org>
2007-05-09 5:54 ` Herbert Xu
2007-05-09 5:58 ` Andrew Morton
2007-05-09 6:11 ` Andrew Morton
2007-05-09 6:22 ` David Miller
2007-05-09 7:16 ` Herbert Xu
2007-05-09 7:18 ` David Miller
2007-05-09 21:11 ` Andrew Morton
2007-05-09 21:39 ` David Miller
2007-05-09 21:45 ` Andrew Morton
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=20070508222033.4e57a580.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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 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).