All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 15341] Load goes up very high when we traverse the large tree
Date: Thu, 25 Feb 2010 13:34:31 GMT	[thread overview]
Message-ID: <201002251334.o1PDYVQH009582@demeter.kernel.org> (raw)
In-Reply-To: <bug-15341-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=15341





--- Comment #15 from Jens Axboe <axboe@kernel.dk>  2010-02-25 13:34:23 ---
OK, that's good at least. We need to do something about 2.6.32, though. If you
are willing to try and bisect the problem, it would be much appreciated.
Checking revisions between 2.6.31 and 2.6.32 for CFQ, there are only 12 of
them. So you would not need to compile and check more than 4 kernels.

The way you would do this, is git clone Linus -git tree:

$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ git checkout v2.6.32

Start the bisect testing:

$ git bisect start block/cfq-iosched.c
$ git bisect good v2.6.31
$ git bisect bad v2.6.32

Now copy in your .config and run make oldconfig and compile the kernel+modules
like you always do. Boot and test the kernel. Lets assume this first test is
good, you'd then cd back into your source directory and do:

$ git bisect good

which would hand you a new revision to build, boot, and test. Likewise, if the
resulting kernel image didn't work well, you would run

$ git bisect bad

instead. You repeat this until git tells you what the bad revision was. And
then you post that here :-)

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-02-25 13:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 11:43 [Bug 15341] New: Load goes up very high when we traverse the large tree bugzilla-daemon
2010-02-17 11:44 ` [Bug 15341] " bugzilla-daemon
2010-02-18  3:18 ` bugzilla-daemon
2010-02-18  3:19 ` bugzilla-daemon
2010-02-19 13:23 ` bugzilla-daemon
2010-02-19 17:01 ` bugzilla-daemon
2010-02-19 17:33 ` bugzilla-daemon
2010-02-19 17:35 ` bugzilla-daemon
2010-02-19 17:55 ` bugzilla-daemon
2010-02-19 21:01 ` bugzilla-daemon
2010-02-23 12:38 ` bugzilla-daemon
2010-02-23 18:37 ` bugzilla-daemon
2010-02-23 22:24 ` bugzilla-daemon
2010-02-25 12:04 ` bugzilla-daemon
2010-02-25 12:06 ` bugzilla-daemon
2010-02-25 12:06 ` bugzilla-daemon
2010-02-25 13:34 ` bugzilla-daemon [this message]
2010-03-05 18:48 ` bugzilla-daemon
2010-02-21 21:38 2.6.33-rc8-git6: Reported regressions 2.6.31 -> 2.6.32 Rafael J. Wysocki
2010-02-21 21:42 ` [Bug #15341] Load goes up very high when we traverse the large tree Rafael J. Wysocki
     [not found] <bug-15341-11613@https.bugzilla.kernel.org/>
2010-04-09 19:31 ` [Bug 15341] " bugzilla-daemon
2010-10-02 20:59 ` bugzilla-daemon
2010-10-07 19:58 ` bugzilla-daemon
2011-02-02 20:55 ` bugzilla-daemon
2011-02-03  8:44 ` bugzilla-daemon

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=201002251334.o1PDYVQH009582@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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.