Re: ps/reftable-optimize-io (was: What's cooking in git.git (Jan 2024, #06; Fri, 19))

From: Patrick Steinhardt <ps@pks.im>
Date: Jan 23, 2024, 08:23 UTC
Message-ID: <Za93haRpKqksqktG@tanuki>
In-Reply-To: <xmqqbk9ghio5.fsf@gitster.g>

On Fri, Jan 19, 2024 at 05:56:10PM -0800, Junio C Hamano wrote:

Show 16 quoted lines

> * ps/reftable-optimize-io (2024-01-18) 7 commits
>  - reftable/stack: fix race in up-to-date check
>  - reftable/stack: unconditionally reload stack after commit
>   (merged to 'next' on 2024-01-12 at 4096e880e0)
>  + reftable/blocksource: use mmap to read tables
>  + reftable/blocksource: refactor code to match our coding style
>  + reftable/stack: use stat info to avoid re-reading stack list
>  + reftable/stack: refactor reloading to use file descriptor
>  + reftable/stack: refactor stack reloading to have common exit path
> 
>  Low-level I/O optimization for reftable.
> 
>  The two commits at the tip are new.
>  Will merge to 'next' and then to 'master'?
>  source: <cover.1704966670.git.ps@pks.im>
>  source: <cover.1705585037.git.ps@pks.im>

Yeah, this topic is good to go from my point of view.

Patrick