From: Hugh Dickins <hugh@veritas.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Ross Biro <rossb@google.com>,
linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Page Faults slower in 2.6.25-rc9 than 2.6.23
Date: Wed, 30 Apr 2008 12:33:53 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0804301215080.4651@blonde.site> (raw)
In-Reply-To: <20080430135035.b0b02533.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 30 Apr 2008, KAMEZAWA Hiroyuki wrote:
> On Tue, 29 Apr 2008 09:10:36 -0400
> "Ross Biro" <rossb@google.com> 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.
>
> It seems lmbench's pagefault program uses 'page fault by READ'.
> Then, this patch affects. (this patch was added at 2.6.24-rc?.)
> ==
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=557ed1fa2620dc119adb86b34c614e152a629a80
> ==
> By it, ZERO_PAGE is not used for page fault in anonymous mapping.
I'd wondered about that one too, but no: lmbench lat_pagefault uses
a shared mmap of an ordinary file (not /dev/zero), so the ZERO_PAGE
changes should have no effect on it whatsoever.
I notice that test is expecting msync(,,MS_INVALIDATE) to do something
it's never done on Linux (a kind of drop caches for the range). We've
never done anything with MS_INVALIDATE, beyond permitting the flag:
I think you find problems however you try to go about implementing
it (and it might even originate from a UNIX which couldn't do shared
mmap coherently). So I wonder if that test is erratic because of it.
Hugh
--
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>
prev parent reply other threads:[~2008-04-30 11:33 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
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 [this message]
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=Pine.LNX.4.64.0804301215080.4651@blonde.site \
--to=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.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