From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: ps/reftable-optimize-io (was: What's cooking in git.git (Jan 2024, #06; Fri, 19))
Date: Tue, 23 Jan 2024 09:23:33 +0100 [thread overview]
Message-ID: <Za93haRpKqksqktG@tanuki> (raw)
In-Reply-To: <xmqqbk9ghio5.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Fri, Jan 19, 2024 at 05:56:10PM -0800, Junio C Hamano wrote:
> * 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-23 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 1:56 What's cooking in git.git (Jan 2024, #06; Fri, 19) Junio C Hamano
2024-01-20 2:10 ` Ghanshyam Thakkar
2024-01-20 17:19 ` Junio C Hamano
2024-01-23 8:23 ` Patrick Steinhardt [this message]
2024-01-23 21:25 ` sd/negotiate-trace-fix (was: What's cooking in git.git (Jan 2024, #06; Fri, 19)) Josh Steadmon
2024-01-23 21:34 ` sd/negotiate-trace-fix Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Za93haRpKqksqktG@tanuki \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).