From: Christoph Hellwig <hch@infradead.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [S390] minor fault path optimization.
Date: Mon, 19 Mar 2007 13:31:49 +0000 [thread overview]
Message-ID: <20070319133149.GA5781@infradead.org> (raw)
In-Reply-To: <20070319130206.GC1292@skybase>
On Mon, Mar 19, 2007 at 02:02:06PM +0100, Martin Schwidefsky wrote:
> From: Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> [S390] minor fault path optimization.
>
> The minor fault path has grown a lot in terms of cycles. In particular
> the kprobes hook is very costly. Optimize the path to save a couple of
> cycles. If kprobes is enabled more than 300 cycles can be avoided if
> kprobes_running() is false.
Actually there is a lot more fishy here. This code is duplicated over
every single architecture. It uses a notifier chain that only ever has
one actual uaesr. It exports interfaces that are potential harmful.
Please do the right thing to optimize this instead and rip out the brandead
notifier chain mechanisms and directly call into the krobes handler if
kprobes are active, in particular the DIE_PAGE_FAULT: case of
kprobe_exceptions_notify. That allows you to optimize the path both
if kprobes are active, and even further if they're not.
The same should be done for all other architectures, and the other
(ab-)uses of the kprobes notifiers.
next parent reply other threads:[~2007-03-19 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070319130206.GC1292@skybase>
2007-03-19 13:31 ` Christoph Hellwig [this message]
2007-03-19 14:00 ` [S390] minor fault path optimization Andi Kleen
2007-03-19 14:08 ` [PATCH] powerpc minor pagefault optimization with kprobes enabled Christoph Hellwig
2007-03-20 5:12 ` Anton Blanchard
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=20070319133149.GA5781@infradead.org \
--to=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).