From: patchwork-bot+linux-riscv@kernel.org
To: Evan Green <evan@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
apatel@ventanamicro.com, aou@eecs.berkeley.edu, heiko@sntech.de,
leyfoon.tan@starfivetech.com, maz@kernel.org,
bigeasy@linutronix.de, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, conor.dooley@microchip.com,
David.Laight@aculab.com, palmer@dabbelt.com, jszhang@kernel.org,
greentime.hu@sifive.com, cleger@rivosinc.com,
ajones@ventanamicro.com
Subject: Re: [PATCH v3] RISC-V: Probe misaligned access speed in parallel
Date: Wed, 08 Nov 2023 15:10:23 +0000 [thread overview]
Message-ID: <169945622394.21527.3124390235718223224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231106225855.3121724-1-evan@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 6 Nov 2023 14:58:55 -0800 you wrote:
> Probing for misaligned access speed takes about 0.06 seconds. On a
> system with 64 cores, doing this in smp_callin() means it's done
> serially, extending boot time by 3.8 seconds. That's a lot of boot time.
>
> Instead of measuring each CPU serially, let's do the measurements on
> all CPUs in parallel. If we disable preemption on all CPUs, the
> jiffies stop ticking, so we can do this in stages of 1) everybody
> except core 0, then 2) core 0. The allocations are all done outside of
> on_each_cpu() to avoid calling alloc_pages() with interrupts disabled.
>
> [...]
Here is the summary with links:
- [v3] RISC-V: Probe misaligned access speed in parallel
https://git.kernel.org/riscv/c/55e0bf49a0d0
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:[~2023-11-08 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 22:58 Evan Green
2023-11-07 8:34 ` Sebastian Andrzej Siewior
2023-11-07 17:26 ` Evan Green
2023-11-07 17:45 ` Palmer Dabbelt
2023-11-08 15:10 ` 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=169945622394.21527.3124390235718223224.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=David.Laight@aculab.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=bigeasy@linutronix.de \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®