From: patchwork-bot+linux-riscv@kernel.org
To: David Wang <00107082@163.com>
Cc: linux-riscv@lists.infradead.org, tglx@linutronix.de,
richard.henderson@linaro.org, linux@armlinux.org.uk,
catalin.marinas@arm.com, will@kernel.org, guoren@kernel.org,
chenhuacai@kernel.org, kernel@xen0n.name,
James.Bottomley@HansenPartnership.com, deller@gmx.de,
mpe@ellerman.id.au, paul.walmsley@sifive.com,
ysato@users.sourceforge.jp, dalias@libc.org,
glaubitz@physik.fu-berlin.de, davem@davemloft.net,
andreas@gaisler.com, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, chris@zankel.net,
jcmvbkbc@gmail.com, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
loongarch@lists.linux.dev, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH] kernel/irq/proc: performance: replace seq_printf with seq_put_decimal_ull_width
Date: Wed, 11 Dec 2024 22:32:46 +0000 [thread overview]
Message-ID: <173395636600.1729195.17930169527159894833.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241103080552.4787-1-00107082@163.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Michael Ellerman <mpe@ellerman.id.au>:
On Sun, 3 Nov 2024 16:05:52 +0800 you wrote:
> seq_printf is costy, when stress reading /proc/interrupts, profiling indicates
> seq_printf takes about ~47% of show_interrupts samples:
>
> show_interrupts(94.495% 5166019/5466991)
> seq_printf(47.429% 2450210/5166019)
> vsnprintf(89.232% 2186366/2450210)
> format_decode(24.005% 524831/2186366)
> number(19.488% 426084/2186366)
> memcpy_orig(3.739% 81753/2186366)
> ...
> _raw_spin_unlock_irqrestore(26.643% 1376379/5166019)
> mtree_load(8.059% 416304/5166019)
>
> [...]
Here is the summary with links:
- kernel/irq/proc: performance: replace seq_printf with seq_put_decimal_ull_width
https://git.kernel.org/riscv/c/5b881c1f8379
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-12-11 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 8:05 [PATCH] kernel/irq/proc: performance: replace seq_printf with seq_put_decimal_ull_width David Wang
2024-11-08 14:25 ` Thomas Gleixner
2024-11-08 15:28 ` David Wang
2024-12-11 22:32 ` patchwork-bot+linux-riscv [this message]
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=173395636600.1729195.17930169527159894833.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=00107082@163.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andreas@gaisler.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=chris@zankel.net \
--cc=dalias@libc.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guoren@kernel.org \
--cc=jcmvbkbc@gmail.com \
--cc=kernel@xen0n.name \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paul.walmsley@sifive.com \
--cc=richard.henderson@linaro.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).