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,
maz@kernel.org, linux-kernel@vger.kernel.org,
conor.dooley@microchip.com, David.Laight@aculab.com,
palmer@dabbelt.com, jszhang@kernel.org, paul.walmsley@sifive.com,
greentime.hu@sifive.com, ajones@ventanamicro.com
Subject: Re: [PATCH v2] RISC-V: Probe misaligned access speed in parallel
Date: Thu, 02 Nov 2023 20:20:30 +0000 [thread overview]
Message-ID: <169895643056.22248.6956745778026886386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920193801.3035093-1-evan@rivosinc.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 20 Sep 2023 12:38:01 -0700 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.
>
> [...]
Here is the summary with links:
- [v2] RISC-V: Probe misaligned access speed in parallel
https://git.kernel.org/riscv/c/0c37376609da
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-11-02 20:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 19:38 [PATCH v2] RISC-V: Probe misaligned access speed in parallel Evan Green
2023-09-20 21:03 ` Conor Dooley
2023-09-20 21:27 ` Atish Patra
2023-09-20 22:06 ` Evan Green
2023-09-20 22:25 ` Conor Dooley
2023-09-29 11:19 ` Conor Dooley
2023-09-20 22:57 ` Atish Patra
2023-09-20 23:54 ` Evan Green
2023-09-21 10:22 ` David Laight
2023-09-21 16:44 ` Evan Green
2023-09-21 16:49 ` Evan Green
2023-09-21 2:41 ` Jisheng Zhang
2023-11-02 20:20 ` 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=169895643056.22248.6956745778026886386.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=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=heiko@sntech.de \
--cc=jszhang@kernel.org \
--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