From: Junio C Hamano <email@example.com> To: Elijah Newren <firstname.lastname@example.org> Cc: Goss Geppert <email@example.com>, Git Mailing List <firstname.lastname@example.org>, christian w <email@example.com>, Derrick Stolee <firstname.lastname@example.org> Subject: Re: [PATCH v2 1/2] dir: consider worktree config in path recursion Date: Tue, 24 May 2022 12:45:37 -0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CABPp-BGXRzYCvyM38dEUvQ125+VtRu++7L9UiRz98u+1=Lov7A@mail.gmail.com> (Elijah Newren's message of "Tue, 24 May 2022 07:29:09 -0700") Elijah Newren <firstname.lastname@example.org> writes: > On Wed, May 11, 2022 at 9:37 AM Junio C Hamano <email@example.com> wrote: >> >> Goss Geppert <firstname.lastname@example.org> writes: >> >> > diff --git a/dir.c b/dir.c >> > index f2b0f24210..a1886e61a3 100644 >> > --- a/dir.c >> > +++ b/dir.c >> > @@ -1893,9 +1893,31 @@ static enum path_treatment treat_directory(struct dir_struct *dir, >> > [...] >> >> > + real_gitdir = real_pathdup(the_repository->gitdir, 0); >> >> This function is repeatedly called during the traversal. >> >> How expensive is it to keep calling real_pathdup() on the constant >> the_repository->gitdir just in case it might be the same as our true >> GIT_DIR? > > I agree that treat_directory is called many times, but this > real_pathdup() call is inside the "if (nested_repo)" block, so this > new real_pathdup() invocation should occur very seldom. Or are you > worried about cases where users have *very* large numbers of bare > repositories nested under the working directory? No. I wasn't worried about anything in particular. I just wanted to get the feel of how deep a thought the patch was backed by by spot checking what was and what was not taken into account when designing the change. I do not care too much when there are very large numbers of things that cause this codepath to be exercised. Strange situations can be left for later optimization only when they turn up in the real world and prove to be a problem. By the way, where is a bare repository involved? did you mean non-bare aka worktree-full repository?
next prev parent reply other threads:[~2022-05-24 19:45 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-05 20:32 [RFC PATCH 0/1] " Goss Geppert 2022-05-05 20:32 ` [RFC PATCH 1/1] " Goss Geppert 2022-05-07 3:26 ` Elijah Newren 2022-05-07 17:59 ` oss dev 2022-05-06 17:02 ` [RFC PATCH 0/1] " Junio C Hamano 2022-05-06 20:00 ` oss dev 2022-05-10 17:15 ` [PATCH v2 0/2] " Goss Geppert 2022-05-10 17:15 ` [PATCH v2 1/2] " Goss Geppert 2022-05-11 16:37 ` Junio C Hamano 2022-05-20 19:45 ` oss dev 2022-05-24 14:29 ` Elijah Newren 2022-05-24 19:45 ` Junio C Hamano [this message] 2022-05-25 3:46 ` Elijah Newren 2022-05-11 23:07 ` Junio C Hamano 2022-05-20 20:01 ` oss dev 2022-05-23 19:23 ` Derrick Stolee 2022-05-30 18:48 ` oss dev 2022-05-10 17:15 ` [PATCH v2 2/2] dir: minor refactoring / clean-up Goss Geppert 2022-05-11 16:51 ` Junio C Hamano 2022-05-20 20:03 ` oss dev 2022-05-20 19:28 ` [PATCH v3 0/3] dir: traverse into repository Goss Geppert 2022-05-20 19:28 ` [PATCH v3 1/3] " Goss Geppert 2022-05-20 19:28 ` [PATCH v3 2/3] dir: cache git_dir's realpath Goss Geppert 2022-05-24 14:32 ` Elijah Newren 2022-05-20 19:28 ` [PATCH v3 3/3] dir: minor refactoring / clean-up Goss Geppert 2022-06-16 23:19 ` [PATCH v4 0/2] dir: traverse into repository Goss Geppert 2022-06-22 4:57 ` Elijah Newren [not found] ` <email@example.com> 2022-06-16 23:19 ` [PATCH v4 1/2] " Goss Geppert 2022-06-16 23:44 ` [PATCH v4 0/2] dir: traverse into repository (resending) Goss Geppert [not found] ` <firstname.lastname@example.org> 2022-06-16 23:44 ` [PATCH v4 1/2] dir: traverse into repository Goss Geppert 2022-06-16 23:44 ` [PATCH v4 2/2] dir: minor refactoring / clean-up Goss Geppert
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v2 1/2] dir: consider worktree config in path recursion' \ /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
Code repositories for project(s) associated with this 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).