From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: "M.Jagadish Kumar" <jagadish@rishi.serc.iisc.ernet.in>,
linux-mm@kvack.org
Subject: Re: page fault.
Date: Thu, 26 Oct 2000 13:44:28 -0700 [thread overview]
Message-ID: <39F897AC.4A97EAD3@sgi.com> (raw)
In-Reply-To: <8ta1ir$358it$1@fido.engr.sgi.com>
"M.Jagadish Kumar" wrote:
>
> hello,
> Is there any way in which i can know when the pagefault occured,
> i mean at what instruction of my program execution.
> Does OS provide any support. This would help me to improve my program.
Unless the test program is the only one on the system,
there are other programs which will affect the pagefault
of the test program, since the pages of those other programs
affect the resident pages of the test program.
AFAICT, there is no direct means of saying which instructions
caused page faults ... things like /sbin/time can report
total page faults only.
Why are you specifically interested in page faults?
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
--
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.eu.org/Linux-MM/
next parent reply other threads:[~2000-10-26 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8ta1ir$358it$1@fido.engr.sgi.com>
2000-10-26 20:44 ` Rajagopal Ananthanarayanan [this message]
2000-10-26 15:58 ptes flags in compressed cache Stephen C. Tweedie
2000-10-27 2:12 ` page fault M.Jagadish Kumar
2000-10-26 19:45 ` afei
2000-10-26 19:53 ` Rik van Riel
2000-10-27 2:14 ` afei
2000-10-27 11:17 ` Stephen C. Tweedie
[not found] ` <8tboe4$3bfb7$1@fido.engr.sgi.com>
2000-10-27 17:38 ` Rajagopal Ananthanarayanan
2000-10-30 12:19 ` volodya
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=39F897AC.4A97EAD3@sgi.com \
--to=ananth@sgi.com \
--cc=jagadish@rishi.serc.iisc.ernet.in \
--cc=linux-mm@kvack.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