From: git@jeffhostetler.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v4 0/4] read-cache: call verify_hdr() in a background thread
Date: Mon, 3 Apr 2017 18:53:02 +0000 [thread overview]
Message-ID: <20170403185306.36164-1-git@jeffhostetler.com> (raw)
From: Jeff Hostetler <jeffhost@microsoft.com>
Version 4 of this patch series incorporates the cleanup made by Junio
to my 3rd veresion, updates fsck to always verify the checksum, and a
new simplified perf test using p0002 as discussed on the mailing list.
================
Version 3 of this patch series simplifies this effort to just turn
on/off the hash verification using a "core.checksumindex" config variable.
I've preserved the original checksum validation code so that we can
force it on in fsck if desired.
It eliminates the original threading model completely.
Jeff Hostetler (4):
read-cache: core.checksumindex
fsck: force core.checksumindex=1
t1450-fsck: test core.checksumindex
p0002-read-cache: test core.checksumindex
Documentation/config.txt | 8 ++++++++
builtin/fsck.c | 1 +
cache.h | 7 +++++++
read-cache.c | 18 ++++++++++++++++++
t/perf/p0002-read-cache.sh | 8 +++++++-
t/t1450-fsck.sh | 27 +++++++++++++++++++++++++++
6 files changed, 68 insertions(+), 1 deletion(-)
--
2.9.3
next reply other threads:[~2017-04-03 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 18:53 git [this message]
2017-04-03 18:53 ` [PATCH v4 1/4] read-cache: core.checksumindex git
2017-04-03 18:53 ` [PATCH v4 2/4] fsck: force core.checksumindex=1 git
2017-04-03 20:31 ` Ævar Arnfjörð Bjarmason
2017-04-04 2:29 ` Jeff King
2017-04-04 8:23 ` Ævar Arnfjörð Bjarmason
2017-04-04 8:27 ` Jeff King
2017-04-04 13:13 ` Jeff Hostetler
2017-04-04 20:18 ` Jeff King
2017-04-03 18:53 ` [PATCH v4 3/4] t1450-fsck: test core.checksumindex git
2017-04-03 18:53 ` [PATCH v4 4/4] p0002-read-cache: " git
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=20170403185306.36164-1-git@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.