From: Derrick Stolee <stolee@gmail.com>
To: "René Scharfe" <l.s.r@web.de>,
"SZEDER Gábor via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: me@ttaylorr.com, szeder.dev@gmail.com,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH v2 06/11] commit-graph: simplify chunk writes into loop
Date: Thu, 25 Jun 2020 10:59:22 -0400 [thread overview]
Message-ID: <467ecf3b-2635-5d92-c8f9-9e89dd6580ee@gmail.com> (raw)
In-Reply-To: <675f46df-c57c-bcd6-3f6a-fdd40b2f3066@web.de>
On 6/25/2020 3:25 AM, René Scharfe wrote:
> Am 23.06.20 um 19:47 schrieb SZEDER Gábor via GitGitGadget:
>> From: =?UTF-8?q?SZEDER=20G=C3=A1bor?= <szeder.dev@gmail.com>
>>
>> In write_commit_graph_file() we now have one block of code filling the
>> array of 'struct chunk_info' with the IDs and sizes of chunks to be
>> written, and an other block of code calling the functions responsible
>> for writing individual chunks. In case of optional chunks like Extra
>> Edge List an Base Graphs List there is also a condition checking
>> whether that chunk is necessary/desired, and that same condition is
>> repeated in both blocks of code. Other, newer chunks have similar
>> optional conditions.
>>
>> Eliminate these repeated conditions by storing the function pointers
>> responsible for writing individual chunks in the 'struct chunk_info'
>> array as well, and calling them in a loop to write the commit-graph
>> file. This will open up the possibility for a bit of foolproofing in
>> the following patch.
>
> You can do that without storing function pointers by selecting the
> function to use based on the chunk ID -- like parse_commit_graph() does
> on the read side. Advantage: You don't need to press all write
> functions into the same mold and can keep their individual signatures.
I do think that the loop without a switch statement is valuable.
It focuses the updates for new chunks to be localized to the
section that calculates the offset values.
>>
>> Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
>> Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
>> ---
>> commit-graph.c | 31 +++++++++++++++++++------------
>> 1 file changed, 19 insertions(+), 12 deletions(-)
>>
>> diff --git a/commit-graph.c b/commit-graph.c
>> index f33bfe49b3..086fc2d070 100644
>> --- a/commit-graph.c
>> +++ b/commit-graph.c
>> @@ -1555,9 +1555,13 @@ static int write_graph_chunk_base(struct hashfile *f,
>> return 0;
>> }
>>
>> +typedef int (*chunk_write_fn)(struct hashfile *f,
>> + struct write_commit_graph_context *ctx);
>> +
>> struct chunk_info {
>> uint32_t id;
>> uint64_t size;
>> + chunk_write_fn write_fn;
>> };
>>
>> static int write_commit_graph_file(struct write_commit_graph_context *ctx)
>> @@ -1615,27 +1619,34 @@ static int write_commit_graph_file(struct write_commit_graph_context *ctx)
>>
>> chunks[0].id = GRAPH_CHUNKID_OIDFANOUT;
>> chunks[0].size = GRAPH_FANOUT_SIZE;
>> + chunks[0].write_fn = write_graph_chunk_fanout;
>> chunks[1].id = GRAPH_CHUNKID_OIDLOOKUP;
>> chunks[1].size = hashsz * ctx->commits.nr;
>> + chunks[1].write_fn = write_graph_chunk_oids;
>> chunks[2].id = GRAPH_CHUNKID_DATA;
>> chunks[2].size = (hashsz + 16) * ctx->commits.nr;
>> + chunks[2].write_fn = write_graph_chunk_data;
>> if (ctx->num_extra_edges) {
>> chunks[num_chunks].id = GRAPH_CHUNKID_EXTRAEDGES;
>> chunks[num_chunks].size = 4 * ctx->num_extra_edges;
>> + chunks[num_chunks].write_fn = write_graph_chunk_extra_edges;
>> num_chunks++;
>> }
>> if (ctx->changed_paths) {
>> chunks[num_chunks].id = GRAPH_CHUNKID_BLOOMINDEXES;
>> chunks[num_chunks].size = sizeof(uint32_t) * ctx->commits.nr;
>> + chunks[num_chunks].write_fn = write_graph_chunk_bloom_indexes;
>> num_chunks++;
>> chunks[num_chunks].id = GRAPH_CHUNKID_BLOOMDATA;
>> chunks[num_chunks].size = sizeof(uint32_t) * 3
>> + ctx->total_bloom_filter_data_size;
>> + chunks[num_chunks].write_fn = write_graph_chunk_bloom_data;
>> num_chunks++;
>> }
>> if (ctx->num_commit_graphs_after > 1) {
>> chunks[num_chunks].id = GRAPH_CHUNKID_BASE;
>> chunks[num_chunks].size = hashsz * (ctx->num_commit_graphs_after - 1);
>> + chunks[num_chunks].write_fn = write_graph_chunk_base;
>> num_chunks++;
>> }
>>
>> @@ -1671,19 +1682,15 @@ static int write_commit_graph_file(struct write_commit_graph_context *ctx)
>> progress_title.buf,
>> num_chunks * ctx->commits.nr);
>> }
>> - write_graph_chunk_fanout(f, ctx);
>> - write_graph_chunk_oids(f, ctx);
>> - write_graph_chunk_data(f, ctx);
>> - if (ctx->num_extra_edges)
>> - write_graph_chunk_extra_edges(f, ctx);
>> - if (ctx->changed_paths) {
>> - write_graph_chunk_bloom_indexes(f, ctx);
>> - write_graph_chunk_bloom_data(f, ctx);
>> - }
>> - if (ctx->num_commit_graphs_after > 1 &&
>> - write_graph_chunk_base(f, ctx)) {
>> - return -1;
>> +
>> + for (i = 0; i < num_chunks; i++) {
>> + if (chunks[i].write_fn(f, ctx)) {
>> + error(_("failed writing chunk with id %"PRIx32""),
>> + chunks[i].id);
>
> Of all the write functions only write_graph_chunk_base() can return
> non-zero and it already prints an error message in that case ("failed to
> write correct number of base graph ids"). Why add this one?
Ok, we can require the chunk methods to write an error() message with
appropriate context and simply return -1 here.
Thanks,
-Stolee
next prev parent reply other threads:[~2020-06-25 14:59 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:14 [PATCH 0/8] More commit-graph/Bloom filter improvements Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 1/8] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-19 12:58 ` Derrick Stolee
2020-06-15 20:14 ` [PATCH 2/8] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-15 20:14 ` [PATCH 3/8] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-18 20:30 ` René Scharfe
2020-06-15 20:14 ` [PATCH 4/8] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-15 20:14 ` [PATCH 5/8] commit-graph: check all leading directories in changed path Bloom filters SZEDER Gábor via GitGitGadget
2020-06-18 20:31 ` René Scharfe
2020-06-19 9:14 ` René Scharfe
2020-06-19 17:17 ` Taylor Blau
2020-06-19 17:19 ` Taylor Blau
2020-06-23 13:47 ` Derrick Stolee
2020-06-15 20:14 ` [PATCH 6/8] bloom: enforce a minimum size of 8 bytes Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 7/8] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-15 20:14 ` [PATCH 8/8] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-17 21:21 ` [PATCH 0/8] More commit-graph/Bloom filter improvements Junio C Hamano
2020-06-18 1:46 ` Derrick Stolee
2020-06-23 17:46 ` [PATCH v2 00/11] " Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 01/11] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 02/11] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 03/11] bloom: get_bloom_filter() cleanups Derrick Stolee via GitGitGadget
2020-06-25 7:24 ` René Scharfe
2020-06-23 17:47 ` [PATCH v2 04/11] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 05/11] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-23 17:47 ` [PATCH v2 06/11] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 14:59 ` Derrick Stolee [this message]
2020-06-23 17:47 ` [PATCH v2 07/11] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 15:02 ` Derrick Stolee
2020-06-23 17:47 ` [PATCH v2 08/11] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 09/11] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-06-23 17:47 ` [PATCH v2 10/11] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
2020-06-25 7:25 ` René Scharfe
2020-06-25 15:05 ` Derrick Stolee
2020-06-26 6:34 ` SZEDER Gábor
2020-06-26 14:42 ` Derrick Stolee
2020-06-23 17:47 ` [PATCH v2 11/11] bloom: enforce a minimum size of 8 bytes Derrick Stolee via GitGitGadget
2020-06-24 23:11 ` [PATCH v2 00/11] More commit-graph/Bloom filter improvements Junio C Hamano
2020-06-24 23:32 ` Derrick Stolee
2020-06-25 0:38 ` Junio C Hamano
2020-06-25 13:38 ` Derrick Stolee
2020-06-25 16:34 ` Junio C Hamano
2020-06-26 12:30 ` [PATCH v3 00/10] " Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 01/10] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 02/10] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 03/10] bloom: fix logic in get_bloom_filter() Derrick Stolee via GitGitGadget
2020-06-27 16:33 ` SZEDER Gábor
2020-06-29 13:02 ` Derrick Stolee
2020-06-26 12:30 ` [PATCH v3 04/10] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 05/10] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 06/10] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 07/10] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 08/10] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 09/10] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-06-26 12:30 ` [PATCH v3 10/10] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 00/10] More commit-graph/Bloom filter improvements Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 01/10] commit-graph: place bloom_settings in context Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 02/10] commit-graph: change test to die on parse, not load Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 03/10] bloom: fix logic in get_bloom_filter() Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 04/10] commit-graph: persist existence of changed-paths Derrick Stolee via GitGitGadget
2020-10-15 13:21 ` SZEDER Gábor
2020-10-15 21:41 ` Taylor Blau
2020-10-16 2:18 ` Derrick Stolee
2020-10-16 3:18 ` Taylor Blau
2020-10-16 13:52 ` Derrick Stolee
2020-07-01 13:27 ` [PATCH v4 05/10] commit-graph: unify the signatures of all write_graph_chunk_*() functions SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 06/10] commit-graph: simplify chunk writes into loop SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 07/10] commit-graph: check chunk sizes after writing SZEDER Gábor via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 08/10] revision.c: fix whitespace Derrick Stolee via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 09/10] revision: empty pathspecs should not use Bloom filters Taylor Blau via GitGitGadget
2020-07-01 13:27 ` [PATCH v4 10/10] commit-graph: check all leading directories in changed path " SZEDER Gábor via GitGitGadget
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=467ecf3b-2635-5d92-c8f9-9e89dd6580ee@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=l.s.r@web.de \
--cc=me@ttaylorr.com \
--cc=szeder.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).