From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: jnareb@gmail.com, stolee@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v3 1/4] alloc: introduce parsed_commits_count
Date: Sun, 14 Jun 2020 00:27:13 +0530 [thread overview]
Message-ID: <20200613185713.GA73354@Abhishek-Arch> (raw)
In-Reply-To: <xmqq8sgr28yd.fsf@gitster.c.googlers.com>
On Fri, Jun 12, 2020 at 03:52:26PM -0700, Junio C Hamano wrote:
> Abhishek Kumar <abhishekkumar8222@gmail.com> writes:
>
> > static unsigned int alloc_commit_index(struct repository *r)
> > {
> > - return r->parsed_objects->commit_count++;
> > + static unsigned int parsed_commits_count = 0;
> > + r->parsed_objects->commit_count++;
> > + return parsed_commits_count++;
> > }
>
> I'll queue this as-is, together with the rest of the series, but
> with the following SQUASH??? to document why we are counting
> globally.
>
> I do not think r->parsed_objects->*_count is used by anybody, and we
> probably can eventually get rid of these stats fields, and when that
> happens, we may want to lose the "struct repository *" pointer from
> the functions in the callchain, but not right now.
>
> Thanks.
>
> alloc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/alloc.c b/alloc.c
> index 29f0e3aa80..ee92661b71 100644
> --- a/alloc.c
> +++ b/alloc.c
> @@ -99,6 +99,11 @@ void *alloc_object_node(struct repository *r)
> return obj;
> }
>
> +/*
> + * The returned count is to be used as an index into commit slabs,
> + * that are *NOT* maintained per repository, and that is why a single
> + * global counter is used.
> + */
> static unsigned int alloc_commit_index(struct repository *r)
> {
> static unsigned int parsed_commits_count = 0;
> --
> 2.27.0-90-geebb51ba8c
>
Thanks for taking a closer look. I have created an issue on
gitgitgadget [1] to get rid of commit count and avoid passing repository
to the functions anymore.
[1]: https://github.com/gitgitgadget/git/issues/657
Abhishek
next prev parent reply other threads:[~2020-06-13 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 18:40 [GSoC Patch v3 0/4] Move generation, graph_pos to a slab Abhishek Kumar
2020-06-12 18:40 ` [PATCH v3 1/4] alloc: introduce parsed_commits_count Abhishek Kumar
2020-06-12 20:08 ` Junio C Hamano
2020-06-12 22:00 ` Junio C Hamano
2020-06-12 22:20 ` Junio C Hamano
2020-06-12 22:52 ` Junio C Hamano
2020-06-13 18:57 ` Abhishek Kumar [this message]
2020-06-12 23:16 ` Jakub Narębski
2020-06-12 18:40 ` [PATCH v3 2/4] commit-graph: introduce commit_graph_data_slab Abhishek Kumar
2020-06-13 6:53 ` SZEDER Gábor
2020-06-17 9:18 ` Abhishek Kumar
2020-06-12 18:40 ` [PATCH v3 3/4] commit: move members graph_pos, generation to a slab Abhishek Kumar
2020-06-12 18:40 ` [PATCH v3 4/4] commit-graph: minimize commit_graph_data_slab access Abhishek Kumar
2020-06-12 21:26 ` [GSoC Patch v3 0/4] Move generation, graph_pos to a slab Jakub Narębski
2020-06-14 6:09 [PATCH v3 1/4] alloc: introduce parsed_commits_count Abhishek Kumar
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=20200613185713.GA73354@Abhishek-Arch \
--to=abhishekkumar8222@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=stolee@gmail.com \
--cc=xmqq8sgr28yd.fsf@gitster.c.googlers.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).