Re: git: 133935d26f20 - main - pf: atomically increment state ids

From: Mateusz Guzik <>
Date: Sat, 08 Oct 2022 22:34:53 UTC
On 10/9/22, Gleb Smirnoff <> wrote:
> On Sat, Oct 08, 2022 at 04:41:29PM +0000, Kristof Provost wrote:
> K> commit 133935d26f20c0b9c433da9a2b32bcbe562bc2c5
> K> Author:     Kristof Provost <>
> K> AuthorDate: 2022-10-07 17:17:06 +0000
> K> Commit:     Kristof Provost <>
> K> CommitDate: 2022-10-08 16:27:29 +0000
> K>
> K>     pf: atomically increment state ids
> K>
> K>     Rather than using a per-cpu state counter, and adding in the CPU id
> we
> K>     can atomically increment the number.
> K>     This has the advantage of removing the assumption that the CPU ID
> fits
> K>     in 8 bits.
> K>
> K>     Event:          Aberdeen Hackathon 2022
> K>     Reviewed by:    mjg
> K>     Differential Revision:
> This adds an atomic operation on a single word on a state creation :(

True, but patching unr64 to be fully scalable is not hard and I intend
to do it later. The point from my end was to not add anything

> Previously two state creations could run in parallel without negatively
> affecting each other.

That's only partially true. For one, the hash tables used (and
associated locking) are not properly aligned to avoid false-sharing.
But even if they were, you still have a lot of hashing conflicts and
associated ping-pong from locking on lookup. And so on. I do have WIP
work introduce lockless lookup here though, but there is technical
debt to clean up.

Mateusz Guzik <mjguzik>