From: Linus Walleij <linus.walleij@linaro.org> To: K Prateek Nayak <kprateek.nayak@amd.com> Cc: linux-kernel@vger.kernel.org, "Gautham R. Shenoy" <gautham.shenoy@amd.com>, Richard Henderson <richard.henderson@linaro.org>, Russell King <linux@armlinux.org.uk>, Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>, Juri Lelli <juri.lelli@redhat.com>, Vincent Guittot <vincent.guittot@linaro.org>, Dietmar Eggemann <dietmar.eggemann@arm.com>, Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>, x86@kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH 00/14] Introducing TIF_NOTIFY_IPI flag Date: Wed, 6 Mar 2024 10:44:50 +0100 [thread overview] Message-ID: <CACRpkdbxjU0r+PDTxJwrgzuJgaKnOCHtkaZtm4jO6bmFQ0SPiQ@mail.gmail.com> (raw) In-Reply-To: <20240220171457.703-1-kprateek.nayak@amd.com> Hi K Prateek, I trimmed down the recipient list so we don't bounce. On Tue, Feb 20, 2024 at 6:15 PM K Prateek Nayak <kprateek.nayak@amd.com> wrote: > Same experiment was repeated on an dual socket ARM server (2 x 64C) > which too saw a significant improvement in the ipistorm performance: > > ================================================================== > Test : ipistorm (modified) > Units : Normalized runtime > Interpretation: Lower is better > Statistic : AMean > ================================================================== > kernel: time [pct imp] > tip:sched/core 1.00 [0.00] > tip:sched/core + TIF_NOTIFY_IPI 0.41 [59.29] Is that a 64bit ARM64 system or really an ARM 32-bit 64-core system? I'm confused because: > K Prateek Nayak (10): > arm/thread_info: Introduce TIF_NOTIFY_IPI flag There is no arm64 patch in the patch series. I can perhaps test the patches on an ARM32 system but all I have is dualcore I think. Yours, Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org> To: K Prateek Nayak <kprateek.nayak@amd.com> Cc: linux-kernel@vger.kernel.org, "Gautham R. Shenoy" <gautham.shenoy@amd.com>, Richard Henderson <richard.henderson@linaro.org>, Russell King <linux@armlinux.org.uk>, Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>, Juri Lelli <juri.lelli@redhat.com>, Vincent Guittot <vincent.guittot@linaro.org>, Dietmar Eggemann <dietmar.eggemann@arm.com>, Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>, x86@kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH 00/14] Introducing TIF_NOTIFY_IPI flag Date: Wed, 6 Mar 2024 10:44:50 +0100 [thread overview] Message-ID: <CACRpkdbxjU0r+PDTxJwrgzuJgaKnOCHtkaZtm4jO6bmFQ0SPiQ@mail.gmail.com> (raw) In-Reply-To: <20240220171457.703-1-kprateek.nayak@amd.com> Hi K Prateek, I trimmed down the recipient list so we don't bounce. On Tue, Feb 20, 2024 at 6:15 PM K Prateek Nayak <kprateek.nayak@amd.com> wrote: > Same experiment was repeated on an dual socket ARM server (2 x 64C) > which too saw a significant improvement in the ipistorm performance: > > ================================================================== > Test : ipistorm (modified) > Units : Normalized runtime > Interpretation: Lower is better > Statistic : AMean > ================================================================== > kernel: time [pct imp] > tip:sched/core 1.00 [0.00] > tip:sched/core + TIF_NOTIFY_IPI 0.41 [59.29] Is that a 64bit ARM64 system or really an ARM 32-bit 64-core system? I'm confused because: > K Prateek Nayak (10): > arm/thread_info: Introduce TIF_NOTIFY_IPI flag There is no arm64 patch in the patch series. I can perhaps test the patches on an ARM32 system but all I have is dualcore I think. Yours, Linus Walleij _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-06 9:45 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-20 17:14 [RFC PATCH 00/14] Introducing TIF_NOTIFY_IPI flag K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 01/14] thread_info: Add helpers to test and clear TIF_NOTIFY_IPI K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 02/14] sched: Define a need_resched_or_ipi() helper and use it treewide K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 03/14] sched/core: Use TIF_NOTIFY_IPI to notify an idle CPU in TIF_POLLING mode of pending IPI K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 04/14] x86/thread_info: Introduce TIF_NOTIFY_IPI flag K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 05/14] arm/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 06/14] alpha/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 07/14] openrisc/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 08/14] powerpc/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 09/14] sh/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 10/14] sparc/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 11/14] csky/thread_info: " K Prateek Nayak 2024-02-23 4:37 ` Guo Ren 2024-02-20 17:14 ` [RFC PATCH 12/14] parisc/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 13/14] nios2/thread_info: " K Prateek Nayak 2024-02-20 17:14 ` [RFC PATCH 14/14] microblaze/thread_info: " K Prateek Nayak 2024-03-06 9:44 ` Linus Walleij [this message] 2024-03-06 9:44 ` [RFC PATCH 00/14] Introducing " Linus Walleij 2024-03-06 10:04 ` K Prateek Nayak 2024-03-06 10:04 ` K Prateek Nayak 2024-03-06 9:59 ` Vincent Guittot 2024-03-06 9:59 ` Vincent Guittot 2024-03-06 10:18 ` K Prateek Nayak 2024-03-06 10:18 ` K Prateek Nayak 2024-03-06 10:28 ` Vincent Guittot 2024-03-06 10:28 ` Vincent Guittot 2024-03-07 19:56 ` Julia Lawall 2024-03-15 6:31 ` K Prateek Nayak
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=CACRpkdbxjU0r+PDTxJwrgzuJgaKnOCHtkaZtm4jO6bmFQ0SPiQ@mail.gmail.com \ --to=linus.walleij@linaro.org \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=dietmar.eggemann@arm.com \ --cc=gautham.shenoy@amd.com \ --cc=juri.lelli@redhat.com \ --cc=kprateek.nayak@amd.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=mingo@redhat.com \ --cc=peterz@infradead.org \ --cc=richard.henderson@linaro.org \ --cc=vincent.guittot@linaro.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.