From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Rusty Lynch <rusty.lynch@intel.com>,
linux-mm@kvack.org, prasanna@in.ibm.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured.
Date: Sat, 27 Aug 2005 00:24:25 +0000 [thread overview]
Message-ID: <200508270224.26423.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508261559450.17433@schroedinger.engr.sgi.com>
On Saturday 27 August 2005 01:05, Christoph Lameter wrote:
> On Fri, 26 Aug 2005, Rusty Lynch wrote:
> > Just to be sure everyone understands the overhead involved, kprobes only
> > registers a single notifier. If kprobes is disabled (CONFIG_KPROBES is
> > off) then the overhead on a page fault is the overhead to execute an
> > empty notifier chain.
>
> Its the overhead of using registers to pass parameters, performing a
> function call that does nothing etc. A waste of computing resources. All
> of that unconditionally in a performance critical execution path that
> is executed a gazillion times for an optional feature that I frankly
> find not useful at all and that is disabled by default.
In the old days notifier_call_chain used to be inline. Then someone looking
at code size out of lined it. Perhaps it should be inlined again or notifier.h
could supply a special faster inline version for time critical code.
Then it would be simple if (global_var != NULL) { ... } in the fast path.
In addition the call chain could be declared __read_mostly.
I suspect with these changes Christoph's concerns would go away, right?
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Rusty Lynch <rusty.lynch@intel.com>,
linux-mm@kvack.org, prasanna@in.ibm.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured.
Date: Sat, 27 Aug 2005 02:24:25 +0200 [thread overview]
Message-ID: <200508270224.26423.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508261559450.17433@schroedinger.engr.sgi.com>
On Saturday 27 August 2005 01:05, Christoph Lameter wrote:
> On Fri, 26 Aug 2005, Rusty Lynch wrote:
> > Just to be sure everyone understands the overhead involved, kprobes only
> > registers a single notifier. If kprobes is disabled (CONFIG_KPROBES is
> > off) then the overhead on a page fault is the overhead to execute an
> > empty notifier chain.
>
> Its the overhead of using registers to pass parameters, performing a
> function call that does nothing etc. A waste of computing resources. All
> of that unconditionally in a performance critical execution path that
> is executed a gazillion times for an optional feature that I frankly
> find not useful at all and that is disabled by default.
In the old days notifier_call_chain used to be inline. Then someone looking
at code size out of lined it. Perhaps it should be inlined again or notifier.h
could supply a special faster inline version for time critical code.
Then it would be simple if (global_var != NULL) { ... } in the fast path.
In addition the call chain could be declared __read_mostly.
I suspect with these changes Christoph's concerns would go away, right?
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Rusty Lynch <rusty.lynch@intel.com>,
linux-mm@kvack.org, prasanna@in.ibm.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured.
Date: Sat, 27 Aug 2005 02:24:25 +0200 [thread overview]
Message-ID: <200508270224.26423.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508261559450.17433@schroedinger.engr.sgi.com>
On Saturday 27 August 2005 01:05, Christoph Lameter wrote:
> On Fri, 26 Aug 2005, Rusty Lynch wrote:
> > Just to be sure everyone understands the overhead involved, kprobes only
> > registers a single notifier. If kprobes is disabled (CONFIG_KPROBES is
> > off) then the overhead on a page fault is the overhead to execute an
> > empty notifier chain.
>
> Its the overhead of using registers to pass parameters, performing a
> function call that does nothing etc. A waste of computing resources. All
> of that unconditionally in a performance critical execution path that
> is executed a gazillion times for an optional feature that I frankly
> find not useful at all and that is disabled by default.
In the old days notifier_call_chain used to be inline. Then someone looking
at code size out of lined it. Perhaps it should be inlined again or notifier.h
could supply a special faster inline version for time critical code.
Then it would be simple if (global_var != NULL) { ... } in the fast path.
In addition the call chain could be declared __read_mostly.
I suspect with these changes Christoph's concerns would go away, right?
-Andi
--
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>
next prev parent reply other threads:[~2005-08-27 0:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 22:46 Re:[PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured Rusty Lynch
2005-08-26 23:05 ` Re:[PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES Christoph Lameter
2005-08-26 23:05 ` Re:[PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured Christoph Lameter
2005-08-26 23:05 ` Christoph Lameter
2005-08-27 0:24 ` Andi Kleen [this message]
2005-08-27 0:24 ` [PATCH] " Andi Kleen
2005-08-27 0:24 ` Andi Kleen
2005-08-30 0:19 ` Rusty Lynch
2005-08-30 0:19 ` Rusty Lynch
2005-08-30 0:19 ` Rusty Lynch
2005-08-30 1:08 ` Andi Kleen
2005-08-30 1:08 ` Andi Kleen
2005-08-30 1:08 ` Andi Kleen
2005-08-30 3:28 ` [PATCH] Only process_die notifier in ia64_do_page_fault if Christoph Lameter
2005-08-30 3:28 ` [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured Christoph Lameter
2005-08-30 3:28 ` Christoph Lameter
2005-08-30 11:18 ` Matthew Wilcox
2005-08-30 11:18 ` Matthew Wilcox
2005-08-30 11:18 ` Matthew Wilcox
2005-09-19 18:22 ` [PATCH] Only process_die notifier in ia64_do_page_fault if Christoph Lameter
2005-09-19 18:22 ` [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured Christoph Lameter
2005-09-19 18:22 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 20:14 Christoph Lameter
2005-08-30 23:05 ` Luck, Tony
2005-08-30 23:05 ` Luck, Tony
2005-08-30 23:05 ` Luck, Tony
2005-08-30 23:38 ` Andi Kleen
2005-08-30 23:38 ` Andi Kleen
2005-08-30 23:38 ` Andi Kleen
2005-08-30 23:54 ` Christoph Lameter
2005-08-30 23:54 ` Christoph Lameter
2005-08-31 0:05 ` Andi Kleen
2005-08-31 0:05 ` Andi Kleen
2005-08-31 0:05 ` Andi Kleen
2005-08-30 23:56 ` David S. Miller
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=200508270224.26423.ak@suse.de \
--to=ak@suse.de \
--cc=anil.s.keshavamurthy@intel.com \
--cc=clameter@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=prasanna@in.ibm.com \
--cc=rusty.lynch@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.