From: "David Wang" <00107082@163.com>
To: "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>
Cc: ysato@users.sourceforge.jp, dalias@libc.org,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 13/13] sh/irq: use seq_put_decimal_ull_width() for decimal values
Date: Sat, 30 Nov 2024 21:34:10 +0800 (CST) [thread overview]
Message-ID: <57371ce2.3933.1937d47626c.Coremail.00107082@163.com> (raw)
In-Reply-To: <a9fe22747f20cae9fcc9b9d20109e7afbf8e6b93.camel@physik.fu-berlin.de>
At 2024-11-30 20:44:26, "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de> wrote:
>Hi David,
>
>On Sat, 2024-11-30 at 13:41 +0100, John Paul Adrian Glaubitz wrote:
>> On Sat, 2024-11-09 at 00:26 +0800, David Wang wrote:
>> > Performance improvement for reading /proc/interrupts on arch sh
>> >
>> > Signed-off-by: David Wang <00107082@163.com>
>> > ---
>> > arch/sh/kernel/irq.c | 4 ++--
>> > 1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/arch/sh/kernel/irq.c b/arch/sh/kernel/irq.c
>> > index 4e6835de54cf..9022d8af9d68 100644
>> > --- a/arch/sh/kernel/irq.c
>> > +++ b/arch/sh/kernel/irq.c
>> > @@ -43,9 +43,9 @@ int arch_show_interrupts(struct seq_file *p, int prec)
>> > {
>> > int j;
>> >
>> > - seq_printf(p, "%*s: ", prec, "NMI");
>> > + seq_printf(p, "%*s:", prec, "NMI");
>> > for_each_online_cpu(j)
>> > - seq_printf(p, "%10u ", per_cpu(irq_stat.__nmi_count, j));
>> > + seq_put_decimal_ull_width(p, " ", per_cpu(irq_stat.__nmi_count, j), 10);
>> > seq_printf(p, " Non-maskable interrupts\n");
>> >
>> > seq_printf(p, "%*s: %10u\n", prec, "ERR", atomic_read(&irq_err_count));
>>
>> Sorry for the very late reply!
>>
>> I don't quite understand why seq_put_decimal_ull_width() should be faster than seq_printf().
>>
>> Can you elaborate on this a bit more?
>
>I just checked existing merges of this patch for other architectures which include
>a more elaborate patch description. If you could do that for SH as well, I can pick
>the patch for v6.14.
>
>Adrian
>
>--
> .''`. John Paul Adrian Glaubitz
>: :' : Debian Developer
>`. `' Physicist
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Sure, I will make the change.
To be honest, I do not have a SH platform to confirm the performance changes.
If convenient, a simple `strace -T -e read cat /proc/interrupts > /dev/null`
can be used to verify any improvement, and the core change in commit
f9ed1f7c2e26fcd1978(genirq/proc: Use seq_put_decimal_ull_width() for decimal values)
is needed.
Thanks
David
next prev parent reply other threads:[~2024-11-30 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:26 David Wang
2024-11-30 12:41 ` John Paul Adrian Glaubitz
2024-11-30 12:44 ` John Paul Adrian Glaubitz
2024-11-30 13:34 ` David Wang [this message]
2024-11-30 13:49 ` [PATCH v2] " David Wang
2025-01-30 8:28 ` John Paul Adrian Glaubitz
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=57371ce2.3933.1937d47626c.Coremail.00107082@163.com \
--to=00107082@163.com \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.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
all inboxes | Powered by JetHome®