From: Jens Axboe <jens.axboe@oracle.com>
To: "Shi, Alex" <alex.shi@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel building regression on 32-rc5 kernel
Date: Tue, 3 Nov 2009 19:32:36 +0100 [thread overview]
Message-ID: <20091103183235.GD8742@kernel.dk> (raw)
In-Reply-To: <F7C8A4D3A9905B45A80E4C194793FA651553C00D3D@PDSMSX501.ccr.corp.intel.com>
On Tue, Nov 03 2009, Shi, Alex wrote:
> I found the kernel building will have about 20%~ 30% regressions on
> our NHM machines. My kernel build do the following things 15 times:
>
> make mrproper; echo \"3\">/proc/sys/vm/drop_caches; make defconfig;
> make -j${2timescpunumbers}
>
>
>
> Bisect found it is due to the commitment:
>
> commit a6151c3a5c8e1ff5a28450bc8d6a99a2a0add0a7
I looked over that commit and found one typo, can you check with this
patch applied?
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index 069a610..5802e32 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
@@ -2051,7 +2051,7 @@ cfq_should_preempt(struct cfq_data *cfqd, struct cfq_queue *new_cfqq,
* it's a metadata request and the current queue is doing regular IO.
*/
if (rq_is_meta(rq) && !cfqq->meta_pending)
- return false;
+ return true;
/*
* Allow an RT request to pre-empt an ongoing non-RT cfqq timeslice.
--
Jens Axboe
next parent reply other threads:[~2009-11-03 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7C8A4D3A9905B45A80E4C194793FA651553C00D3D@PDSMSX501.ccr.corp.intel.com>
2009-11-03 18:32 ` Jens Axboe [this message]
2009-11-04 1:21 ` kernel building regression on 32-rc5 kernel Alex Shi
2009-11-04 7:40 ` Jens Axboe
2009-11-03 14:42 Shi, Alex
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=20091103183235.GD8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=alex.shi@intel.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.