linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Balbir Singh" <balbir@linux.vnet.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ross Biro <rossb@google.com>,
	linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: Page Faults slower in 2.6.25-rc9 than 2.6.23
Date: Tue, 29 Apr 2008 20:22:58 +0530	[thread overview]
Message-ID: <661de9470804290752w1dc0cfb3k72e81d828a45765e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804291447040.5058@blonde.site>

On Tue, Apr 29, 2008 at 7:27 PM, Hugh Dickins <hugh@veritas.com> wrote:
> On Tue, 29 Apr 2008, Ross Biro wrote:
>  > I don't know if this has been noticed before.  I was benchmarking my
>  > page table relocation code and I noticed that on 2.6.25-rc9 page
>  > faults take 10% more time than on 2.6.22.  This is using lmbench
>  > running on an intel x86_64 system.  The good news is that the page
>  > table relocation code now only adds a 1.6% slow down to page faults.
>
>  Do you have CONFIG_CGROUP_MEM_RES_CTLR=y in 2.6.25?
>  That added about 20% to my lmbench "Page Fault" tests (with
>  adverse effect on several others e.g. the fork, exec, sh group).
>

Hmm.. strange.. I don't remember the overhead being so bad (I'll
relook at my old numbers). I'll try and git-bisect this one


>  Try the same kernel with boot option "cgroup_disable=memory",
>  that should recoup most (but not quite all) of the slowdown;
>  or rebuild with n to CGROUP_MEM_RES_CTLR.
>
>  But your "Mmap Latency" went up 425% ??
>

That's really way of the mark

>  Hugh
>

Balbir

--
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>

  parent reply	other threads:[~2008-04-29 14:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 13:10 Ross Biro
2008-04-29 13:57 ` Hugh Dickins
2008-04-29 14:08   ` Ross Biro
2008-04-29 14:52   ` Balbir Singh [this message]
2008-04-29 15:21     ` Ross Biro
2008-04-29 15:32       ` Hugh Dickins
2008-04-29 16:05         ` Ross Biro
2008-04-29 16:42         ` Balbir Singh
2008-04-29 17:00           ` Ross Biro
2008-04-30 13:16             ` Ross Biro
2008-04-30  4:50 ` KAMEZAWA Hiroyuki
2008-04-30 11:33   ` Hugh Dickins

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=661de9470804290752w1dc0cfb3k72e81d828a45765e@mail.gmail.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=hugh@veritas.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rossb@google.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