From: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
To: Anderw Morton <akpm@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Keith Owens <kaos@americas.sgi.com>,
Dean Nelson <dnc@americas.sgi.com>,
Tony Luck <tony.luck@intel.com>,
Ananth Mavinakayanahalli <ananth@in.ibm.com>,
Prasanna Panchamukhi <prasanna@in.ibm.com>,
Dave M <davem@davemloft.net>
Subject: [patch 0/6] Notify page fault call chain
Date: Wed, 19 Apr 2006 12:00:59 -0700 [thread overview]
Message-ID: <20060419190059.452500615@csdlinux-2.jf.intel.com> (raw)
Hi Andrew,
Currently in the do_page_fault() code path, we call notify_die(DIE_PAGE_FAULT, ...)
to notify the page fault. The only interested components for this page fault
notifications are Kprobes and/or kdb. Since notify_die() is highly overloaded,
this page fault notification is currently being sent to other components
registered with register_die_notification() which uses the same die_chain to loop
for all the registered components.
In order to optimize the do_page_fault() code path, this critical page fault notification
is now moved to different call chain and the test results showed great improvements.
Patches for i386, x86_64, ia64, powerpc and sparc64 follows this mail.
Please apply.
Thanks,
Anil Keshavamurthy
--
next reply other threads:[~2006-04-19 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 19:00 Anil S Keshavamurthy [this message]
2006-04-19 19:01 ` [patch 1/6] Notify page fault call chain for i386 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 2/6] Notify page fault call chain for x86_64 Anil S Keshavamurthy
2006-04-19 21:07 ` Andi Kleen
2006-04-19 21:25 ` Keshavamurthy Anil S
2006-04-19 19:01 ` [patch 3/6] Notify page fault call chain for ia64 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 4/6] Notify page fault call chain for powerpc Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 5/6] Notify page fault call chain for sparc64 Anil S Keshavamurthy
2006-04-19 19:01 ` [patch 6/6] Kprobes registers for notify page fault Anil S Keshavamurthy
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=20060419190059.452500615@csdlinux-2.jf.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=dnc@americas.sgi.com \
--cc=kaos@americas.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.