public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: "Meet Soni" <meetsoni3017@gmail•com>,
	git@vger•kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail•com>,
	"Patrick Steinhardt" <ps@pks•im>,
	"Calvin Wan" <calvinwan@google•com>,
	"Elijah Newren" <newren@gmail•com>
Subject: Re: [GSoC][RFC PATCH] show-branch: use commit-slab for flag storage
Date: Fri, 21 Feb 2025 09:15:07 -0800	[thread overview]
Message-ID: <xmqqy0xzb4o4.fsf@gitster.g> (raw)
In-Reply-To: <20250221063257.GA568823@coredump.intra.peff.net> (Jeff King's message of "Fri, 21 Feb 2025 01:32:57 -0500")

Jeff King <peff@peff•net> writes:

> Yeah. I did not see the word "stride" anywhere in your email, so I
> wanted to provide a further hint: the commit-slab "_with_stride()"
> variant is meant to handle this kind of arbitrary-sized data. This was
> part of the original commit-slab implementation in a84b794ad0
> (commit-slab: introduce a macro to define a slab for new type,
> 2013-04-13), but AFAIK we've never actually used it in practice. See
> that commit for some examples.

Wow, after reading the log message of that commit, I realize that we
already were considering that one-bit-per-ref needs dynamic scaling
and folks must have been thinking hard about it (I do not think the
author of the commit alone thought it---it must have been a group
effort on the list, which the log message merely explains the motivation
behind the design).

Thanks for a pointer ;-)

next prev parent reply	other threads:[~2025-02-21 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17  5:50 [GSoC][RFC PATCH] show-branch: use commit-slab for flag storage Meet Soni
2025-02-18 18:40 ` Junio C Hamano
2025-02-21  6:32   ` Jeff King
2025-02-21 17:15     ` Junio C Hamano [this message]
2025-02-25  1:17       ` Jeff King
2025-03-02 12:56   ` Ghanshyam Thakkar

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=xmqqy0xzb4o4.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=avarab@gmail$(echo .)com \
    --cc=calvinwan@google$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=meetsoni3017@gmail$(echo .)com \
    --cc=newren@gmail$(echo .)com \
    --cc=peff@peff$(echo .)net \
    --cc=ps@pks$(echo .)im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox