linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, ant.starikov@gmail.com,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [Bugme-new] [Bug 15618] New: 2.6.18->2.6.32->2.6.33 huge regression in performance
Date: Tue, 23 Mar 2010 18:34:09 +0100	[thread overview]
Message-ID: <20100323173409.GA24845@elte.hu> (raw)
In-Reply-To: <20100323102208.512c16cc.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> lolz.  Catastrophic meltdown.  Thanks for doing all that work - at a guess 
> I'd say it's mmap_sem. [...]

Looks like we dont need to guess, just look at the call graph profile (a'ka 
the smoking gun):

> > I perf'ed on 2.6.32.9-70.fc12.x86_64 kernel
> >
> > [...]
> >
> > callgraph(top part only):
> > 
> > 53.09%      dve22lts-mc  [kernel]                                         [k]
> > _spin_lock_irqsave
> >                |          
> >                |--49.90%-- __down_read_trylock
> >                |          down_read_trylock
> >                |          do_page_fault
> >                |          page_fault
> >                |          |          
> >                |          |--99.99%-- __GI_memcpy
> >                |          |          |          
> >                |          |          |--84.28%-- (nil)
> >                |          |          |          
> >                |          |          |--9.78%-- 0x100000000
> >                |          |          |          
> >                |          |           --5.94%-- 0x1
> >                |           --0.01%-- 
> > [...]
> > 
> >                |          
> >                |--49.39%-- __up_read
> >                |          up_read
> >                |          |          
> >                |          |--100.00%-- do_page_fault
> >                |          |          page_fault
> >                |          |          |          
> >                |          |          |--99.99%-- __GI_memcpy
> >                |          |          |          |          
> >                |          |          |          |--84.18%-- (nil)
> >                |          |          |          |          
> >                |          |          |          |--10.13%-- 0x100000000
> >                |          |          |          |          
> >                |          |          |           --5.69%-- 0x1
> >                |          |           --0.01%-- 
> > [...]

It shows a very brutal amount of page fault invoked mmap_sem spinning 
overhead.

> Perhaps with some assist from the CPU scheduler.

Doesnt look like it, the perf stat numbers show that the scheduler is only 
very lightly involved:

  > > 129875.554435 task-clock-msecs # 10.210 CPUs 
  > >          1883 context-switches # 0.000 M/sec 
 
a context switch only every ~68 milliseconds.

	Ingo
	Ingo

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-03-23 17:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15618-10286@https.bugzilla.kernel.org/>
2010-03-23 14:22 ` Andrew Morton
2010-03-23 17:34   ` Ingo Molnar [this message]
2010-03-23 17:45     ` Linus Torvalds
2010-03-23 17:57       ` Anton Starikov
2010-03-23 18:00       ` Ingo Molnar
2010-03-23 18:03         ` Anton Starikov
2010-03-23 18:21           ` Andrew Morton
2010-03-23 18:25             ` Anton Starikov
2010-03-23 19:22               ` Robin Holt
2010-03-23 19:30                 ` Anton Starikov
2010-03-23 19:49                   ` Robin Holt
2010-03-23 19:57                     ` Robin Holt
2010-03-23 19:50                 ` Anton Starikov
2010-03-23 19:52             ` Linus Torvalds
2010-03-24 16:40           ` Roland Dreier
2010-03-26  3:24             ` Anton Starikov
2010-03-23 19:14       ` Anton Starikov
2010-03-23 19:17         ` Peter Zijlstra
2010-03-23 19:42           ` Anton Starikov
2010-03-23 19:54         ` Linus Torvalds
2010-03-23 20:43           ` Anton Starikov
2010-03-23 23:04             ` Linus Torvalds
2010-03-23 23:19               ` Anton Starikov
2010-03-23 23:36               ` Ingo Molnar
2010-03-23 23:55                 ` Linus Torvalds
2010-03-24  0:03                   ` Anton Starikov
2010-03-24  2:15                   ` Andi Kleen
2010-03-24  3:00                     ` Linus Torvalds
2010-04-19 18:19                       ` Greg KH
2010-03-23 18:13     ` Andrew Morton
2010-03-23 18:19       ` Anton Starikov
2010-03-23 18:27       ` Ingo Molnar
2010-03-23 21:19       ` Anton Starikov
2010-04-02 18:57   ` Lee Schermerhorn

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=20100323173409.GA24845@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=ant.starikov@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.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