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 (Sep 2019, #01; Sat, 7)
Date: Tue, 10 Sep 2019 22:03:42 -0300 [thread overview]
Message-ID: <CAHd-oW4LZTFcoPvqd+FU03+64y7MzesMurCT7tUFQrF_z9ocnQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqd0gcm2zm.fsf@gitster-ct.c.googlers.com>
Hi, Junio
On Sat, Sep 7, 2019 at 2:27 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> * mt/threaded-grep-in-object-store (2019-08-13) 4 commits
> - grep: re-enable threads in some non-worktree cases
> - grep: disable grep_read_mutex when possible
> - grep: allow locks to be enabled individually
> - object-store: add lock to read_object_file_extended()
>
> 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.
>
> Comments?
> cf. <cover.1565468806.git.matheus.bernardino@usp.br>
Just as an update on this, I'm still working on v2 which should also
handle `git-grep --recurse-submodules` in parallel (for the
non-worktree case). So if possible, hold off on this topic a little
longer, please.
Thanks,
Matheus
next prev parent reply other threads:[~2019-09-11 1:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 17:26 What's cooking in git.git (Sep 2019, #01; Sat, 7) Junio C Hamano
2019-09-09 18:58 ` Denton Liu
2019-09-09 19:57 ` Junio C Hamano
2019-09-10 0:18 ` Denton Liu
2019-09-09 23:47 ` brian m. carlson
2019-09-10 0:19 ` Junio C Hamano
2019-09-28 23:31 ` Junio C Hamano
2019-09-28 23:35 ` brian m. carlson
2019-09-10 5:04 ` Martin Ågren
2019-09-10 18:23 ` Josh Steadmon
2019-09-11 1:03 ` Matheus Tavares Bernardino [this message]
2019-09-11 12:01 ` pd/fetch-jobs, was " Johannes Schindelin
2019-09-12 18:02 ` Junio C Hamano
2019-09-14 13:58 ` Palmer Dabbelt
2019-09-16 17:43 ` Junio C Hamano
2019-09-16 20:40 ` Palmer Dabbelt
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-oW4LZTFcoPvqd+FU03+64y7MzesMurCT7tUFQrF_z9ocnQ@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).