From: "Alex,Shi" <alex.shi@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
Corrado Zoccolo <czoccolo@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>, "tytso@mit.edu" <tytso@mit.edu>,
"jaxboe@fusionio.com" <jaxboe@fusionio.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chen, Tim C" <tim.c.chen@intel.com>
Subject: Re: [performance bug] kernel building regression on 64 LCPUs machine
Date: Wed, 23 Feb 2011 16:24:47 +0800 [thread overview]
Message-ID: <1298449487.14712.1064.camel@debian> (raw)
In-Reply-To: <20110221164909.GG6584@quack.suse.cz>
Though these patches can not totally recovered the problem, but they are
quite helpful with ccache enabled situation. It increase 10% performance
on 38-rc1 kernel.
I have tried to enabled they to latest rc6 kernel but failed. the vmstat output is here:
with patches:
r b swpd free buff cache si so bi bo in cs us sy id wa st
1.5 24.7 0.0 64316199.8 17240.8 153376.9 0.0 0.0 1777.1 1788.0 6479.0 2605.3 1.7 0.9 89.1 8.2 0.0
original 38-rc1 kernel:
2.4 32.3 0.0 63653302.9 17170.6 153125.3 0.0 0.0 1579.7 1834.1 6016.4 2407.0 1.5 0.7 86.6 10.1 0.0
It reduce write blocks clearly.
> > can you send a patch with both ext3 and ext4 changes? Our test shows
> > your patch has positive effect, but need confirm with the ext3 change.
> Sure. Patches for both ext3 & ext4 are attached. Sorry, it took me a
> while to get to this.
>
> Honza
next prev parent reply other threads:[~2011-02-23 8:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 1:55 [performance bug] kernel building regression on 64 LCPUs machine Alex,Shi
2011-01-19 2:03 ` Shaohua Li
2011-01-19 12:56 ` Jan Kara
2011-01-20 7:52 ` Alex,Shi
2011-01-20 15:16 ` Vivek Goyal
2011-01-21 7:17 ` Shaohua Li
2011-01-26 8:15 ` Shaohua Li
2011-02-12 9:21 ` Alex,Shi
2011-02-12 18:25 ` Corrado Zoccolo
2011-02-14 2:25 ` Alex,Shi
2011-02-15 1:10 ` Shaohua Li
2011-02-21 16:49 ` Jan Kara
2011-02-23 8:24 ` Alex,Shi [this message]
2011-02-24 12:13 ` Jan Kara
2011-02-25 0:44 ` Alex Shi
2011-02-26 14:45 ` Corrado Zoccolo
2011-03-01 19:56 ` Jeff Moyer
2011-03-02 9:42 ` Jan Kara
2011-03-02 16:13 ` Jeff Moyer
2011-03-02 21:17 ` Jan Kara
2011-03-02 21:20 ` Jeff Moyer
2011-03-03 1:14 ` Jeff Moyer
2011-03-04 15:32 ` Jan Kara
2011-03-04 15:40 ` Jeff Moyer
2011-03-04 15:50 ` Jeff Moyer
2011-03-04 18:27 ` Jeff Moyer
2011-03-22 7:38 ` Alex,Shi
2011-03-22 16:14 ` Jan Kara
2011-03-22 17:46 ` Jeff Moyer
2011-03-24 6:45 ` Alex,Shi
2011-03-28 19:48 ` Jan Kara
2011-01-19 14:32 ` Ted Ts'o
2011-01-20 2:12 ` Shaohua Li
2011-01-21 7:23 ` Corrado Zoccolo
2011-01-21 7:47 ` Alex,Shi
2011-01-21 7:52 ` Alex,Shi
2011-01-21 8:13 ` Corrado Zoccolo
2011-01-21 8:20 ` Shaohua Li
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=1298449487.14712.1064.camel@debian \
--to=alex.shi@intel.com \
--cc=czoccolo@gmail.com \
--cc=jack@suse.cz \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.com \
--cc=tytso@mit.edu \
--cc=vgoyal@redhat.com \
/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).