From: Steven Rostedt <rostedt@goodmis.org>
To: Li kunyu <kunyu@nfschina.com>
Cc: agordeev@linux.ibm.com, aou@eecs.berkeley.edu,
borntraeger@linux.ibm.com, bp@alien8.de,
dave.hansen@linux.intel.com, gor@linux.ibm.com,
hca@linux.ibm.com, hpa@zytor.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux@armlinux.org.uk,
mingo@redhat.com, palmer@dabbelt.com, paul.walmsley@sifive.com,
svens@linux.ibm.com, tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization
Date: Thu, 12 May 2022 11:07:25 -0400 [thread overview]
Message-ID: <20220512110725.22e69e3c@gandalf.local.home> (raw)
In-Reply-To: <20220512144533.58085-1-kunyu@nfschina.com>
On Thu, 12 May 2022 22:45:32 +0800
Li kunyu <kunyu@nfschina.com> wrote:
> I'm glad you're willing to reply to me.
> My current English level is limited, and I may not describe it correctly.
> I consider that these functions may not be modified in a short time,
> which may bring advantages in function performance. I could only submit
> it by inquiry.
The performance improvement is negligible, and not worth the churn (changes
to the code). And if that is the reason for the change, it is not worth
adding it.
Now if the reason for the change is to clean up the code to remove
something that is not used, then it may be something to add if it is not
too intrusive.
-- Steve
next prev parent reply other threads:[~2022-05-12 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 6:30 [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization Li kunyu
2022-05-12 14:12 ` Steven Rostedt
2022-05-12 14:45 ` Li kunyu
2022-05-12 15:07 ` Steven Rostedt [this message]
2022-05-12 15:19 ` Li kunyu
2022-05-13 2:13 ` [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization " Li kunyu
2022-05-17 14:13 ` Steven Rostedt
2022-05-18 2:36 ` [PATCH v2] ftrace: Remove return value of ftrace_arch_modify_*() Li kunyu
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=20220512110725.22e69e3c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=agordeev@linux.ibm.com \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kunyu@nfschina.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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