linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: raz ben yehuda <raziebe@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	riel@redhat.com, kosaki.motohiro@jp.fujitsu.com,
	akpm@linux-foundation.org, Mel Gorman <mel@csn.ul.ie>
Subject: Re: 2.6.38 page_test regression
Date: Thu, 14 Apr 2011 23:07:23 +0300	[thread overview]
Message-ID: <1302811643.10051.8.camel@raz.scalemp.com> (raw)
In-Reply-To: <20110414150925.GD15707@random.random>

bah. Mel is correct. I did mean page_test  ( in my defense it is in the
msg ).
Here some more information:
1. I manage to lower the regression to 2 sha1's:
    	32dba98e085f8b2b4345887df9abf5e0e93bfc12 to
71e3aac0724ffe8918992d76acfe3aad7d8724a5. 
	though I had to remark wait_split_huge_page for the sake of
compilation. up to 32dba98e085f8b2b4345887df9abf5e0e93bfc12 there is no
regression.

2. I booted 2.6.37-rc5 you gave me. same regression is there. 

raz


On Thu, 2011-04-14 at 17:09 +0200, Andrea Arcangeli wrote:
> On Thu, Apr 14, 2011 at 02:49:14PM +0300, raz ben yehuda wrote:
> > Hey Andrea
> > Me again. I managed to ftrace ( function graph ) the two kernels. I used
> > 2.6.37 and 2.6.39-rc3. The bellow is example for sys_brk calls traces
> > from each kernel. As you can see, there is no "single smoking gun"
> > here. 
> > 
> > The vm functions durations increased as a whole.
> > I repeated the tests from sha1 4e9f64c42d0ba5eb0c78569435ada4c224332ce4
> > compared to sha1 152c9ccb75548c027fa3103efa4fa4e19a345449  and it is
> > consistent. ~13% performance decrease.
> > 
> 
> > Can you see any relation to thp that might causes this degradation ?
> 
> With compaction and THP off I don't see how it could change
> anything.
> 
> But can you try the THP-33 tag of my aa.git tree, that was based on
> 2.3.37-rc5 so it'll rule out the whole THP patchset if it doesn't
> regress compared to 2.6.37-rc5 vanilla.
> 
> git clone --reference linux-2.6 git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git
> git checkout THP-33
> 
> Thanks,
> Andrea



  reply	other threads:[~2011-04-14 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1302692638.15225.14.camel@raz.scalemp.com>
     [not found] ` <20110413125146.GR29444@random.random>
2011-04-13 13:48   ` 2.6.38 sbrk regression raz ben yehuda
2011-04-13 14:06   ` raz ben yehuda
2011-04-13 17:21     ` Andrea Arcangeli
2011-04-14  8:13       ` raz ben yehuda
2011-04-14 11:49       ` raz ben yehuda
2011-04-14 15:09         ` Andrea Arcangeli
2011-04-14 20:07           ` raz ben yehuda [this message]
2011-04-14 21:53             ` 2.6.38 page_test regression Mel Gorman
2011-04-14 23:16               ` Mel Gorman
2011-04-14 23:38                 ` Andrea Arcangeli
2011-04-14 23:32               ` Andrea Arcangeli
2011-04-14 23:44                 ` Andrea Arcangeli
2011-04-15  9:11                   ` Mel Gorman

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=1302811643.10051.8.camel@raz.scalemp.com \
    --to=raziebe@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@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).