From: kosaki.motohiro@jp.fujitsu.com (KOSAKI Motohiro)
Subject: [ltt-dev] LTTng 0.87 improved page fault tracing
Date: Thu, 29 Jan 2009 12:42:55 +0900 (JST) [thread overview]
Message-ID: <20090129123827.A959.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20090127210203.GA13478@Krystal>
Hi
interesting..
> I just combined the 4 page fault handler events that were in the tracing
> hot path of LTTng into 2 :
>
> kernel page_fault_entry
> kernel page_fault_exit
>
> They take as parameter the combination of what was available in the
> trap_entry/exit events and handle_mm_fault entry/exit events. This
> should lessen the performance impact of the tracer when it's active.
> I did the related modifications in LTTV 0.12.8.
Just question.
As far as I know, customer has two different requeremtn of the page fault.
(1) collect number of all page fault
-> if it is too large, too many interrupt decrease performance.
(2) collect number of major page fault
-> major page fault indicate to increase random access I/O,
then, some customer want to collect major page fault
(don't include minor page fault)
Is this patch fill (2) requirement?
next prev parent reply other threads:[~2009-01-29 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 21:02 Mathieu Desnoyers
2009-01-29 3:42 ` KOSAKI Motohiro [this message]
2009-01-29 4:43 ` Mathieu Desnoyers
2009-01-29 4:47 ` KOSAKI Motohiro
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=20090129123827.A959.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.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