From: Chris Friesen <cfriesen@nortelnetworks•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Anton Blanchard <anton@samba•org>,
linuxppc-dev@lists•linuxppc.org
Subject: pagetable changes for ppc between 2.6.5 and 2.6.7?
Date: Thu, 19 Aug 2004 11:38:13 -0400 [thread overview]
Message-ID: <4124C965.1020907@nortelnetworks.com> (raw)
I'm seeing some strange behaviour, and before I dove into it I thought I'd
double-check with you guys to see if it was something obvious.
We're running on a dual G5 with a 1.5GB of memory.
We needed a way to track when particular application pages (which would be
mlock'd) were being modified.
We added a bit (_PAGE_MEMMON=0x800) to the PTE flags, and expanded
_PAGE_CHG_MASK to include that bit as well. The new bit signified whether the
page was to be monitored or not.
The app could then (through a driver) mark each page that it wanted to monitor,
and later it could trigger the driver to walk all its page tables, and if the
page was being monitored and was dirty, it would add the page to a list and mark
it as clean. Since the memory was locked, the kernel (we assumed, and it seemed
to work) would never mark the page as clean itself.
Somewhere between 2.6.5 and 2.6.7 the results for identical application runs
changed, and we are now getting far fewer dirty pages. Our assumption is that
something in the kernel is marking pages as clean before we get around to
scanning them. Does anyone know of the top of their heads what would be doing this?
The next step for me is to try running with no swap, just to see if that changes
things. After that, I guess I'll start playing binary search with patches...
Chris
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-08-19 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4124C965.1020907@nortelnetworks.com \
--to=cfriesen@nortelnetworks$(echo .)com \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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