From: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Nov 2019, #02; Fri, 8)
Date: Fri, 8 Nov 2019 12:00:52 -0300 [thread overview]
Message-ID: <CAHd-oW6vBm6JnN8aSeryC716+7xzV-LBZujeRgZgF6RbP0LLHg@mail.gmail.com> (raw)
In-Reply-To: <xmqqeeyin4kx.fsf@gitster-ct.c.googlers.com>
Hi, Junio
On Fri, Nov 8, 2019 at 5:41 AM Junio C Hamano <gitster@pobox.com> wrote:
[...]
>
> * mt/threaded-grep-in-object-store (2019-10-02) 11 commits
> - grep: move driver pre-load out of critical section
> - grep: re-enable threads in non-worktree case
> - grep: protect packed_git [re-]initialization
> - grep: allow submodule functions to run in parallel
> - submodule-config: add skip_if_read option to repo_read_gitmodules()
> - grep: replace grep_read_mutex by internal obj read lock
> - object-store: allow threaded access to object reading
> - replace-object: make replace operations thread-safe
> - grep: fix racy calls in grep_objects()
> - grep: fix race conditions at grep_submodule()
> - grep: fix race conditions on userdiff calls
>
> Traditionally, we avoided threaded grep while searching in objects
> (as opposed to files in the working tree) as accesses to the object
> layer is not thread-safe. This limitation is getting lifted.
>
> What's the current status of this one?
This was the last round of improvements I had in mind for this topic.
So for my part, I think this is ready.
Thanks,
Matheus
next prev parent reply other threads:[~2019-11-08 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 8:40 What's cooking in git.git (Nov 2019, #02; Fri, 8) Junio C Hamano
2019-11-08 15:00 ` Matheus Tavares Bernardino [this message]
2019-11-14 6:35 ` Matheus Tavares Bernardino
2019-11-08 16:44 ` Elijah Newren
2019-11-10 6:59 ` 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=CAHd-oW6vBm6JnN8aSeryC716+7xzV-LBZujeRgZgF6RbP0LLHg@mail.gmail.com \
--to=matheus.bernardino@usp.br \
--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).