From: Naveen N Rao <naveen@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [RFC PATCH] powerpc/ftrace: Refactoring and support for -fpatchable-function-entry
Date: Wed, 07 Jun 2023 22:35:21 +0530 [thread overview]
Message-ID: <1686157010.jpb26wrrqi.naveen@kernel.org> (raw)
In-Reply-To: <11217d67-a9bc-10a9-161c-c73666af0c9b@csgroup.eu>
Christophe Leroy wrote:
>
>
> Le 23/05/2023 à 11:31, Naveen N Rao a écrit :
>> Christophe Leroy wrote:
>>>
>> Ok, I simplified this further, and this is as close to the previous
>> fast path as we can get (applies atop the original RFC). The only
>> difference left is the ftrace_rec iterator.
>
> That's not better, that's even slightly worse (less than 1%).
>
> I will try to investigate why.
I have posted a follow-on RFC with the changes split up:
http://lore.kernel.org/cover.1686151854.git.naveen@kernel.org
Hopefully, that will help narrow down the source of the regression.
- Naveen
next prev parent reply other threads:[~2023-06-07 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 19:26 [RFC PATCH] powerpc/ftrace: Refactoring and support for -fpatchable-function-entry Naveen N Rao
2023-05-20 10:34 ` Christophe Leroy
2023-05-20 16:28 ` Christophe Leroy
2023-05-20 17:48 ` Christophe Leroy
2023-05-20 18:17 ` Naveen N Rao
2023-05-21 9:14 ` Christophe Leroy
2023-05-23 9:31 ` Naveen N Rao
2023-05-26 5:35 ` Christophe Leroy
2023-06-07 17:05 ` Naveen N Rao [this message]
2023-05-20 18:28 ` Naveen N Rao
2023-05-23 13:20 ` Steven Rostedt
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=1686157010.jpb26wrrqi.naveen@kernel.org \
--to=naveen@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).