aboutsummaryrefslogtreecommitdiff
path: root/cache.h
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2011-07-06 19:08:55 -0700
committerJunio C Hamano <gitster@pobox.com>2011-07-06 19:09:29 -0700
commit5f44324d88a6a6699bc30912b26784ac0ade638d (patch)
treec37f1a687887fc003ce4d59fd3251201aba64b30 /cache.h
parent033c2dc4364042b9e6dbd44e82e1974f78a72567 (diff)
downloadgit-5f44324d88a6a6699bc30912b26784ac0ade638d.tar.gz
git-5f44324d88a6a6699bc30912b26784ac0ade638d.tar.xz
core: log offset pack data accesses happened
In a workload other than "git log" (without pathspec nor any option that causes us to inspect trees and blobs), the recency pack order is said to cause the access jump around quite a bit. Add a hook to allow us observe how bad it is. "git config core.logpackaccess /var/tmp/pal.txt" will give you the log in the specified file. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'cache.h')
-rw-r--r--cache.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/cache.h b/cache.h
index f4bb43ec6..16a8c7c23 100644
--- a/cache.h
+++ b/cache.h
@@ -784,6 +784,9 @@ extern int force_object_loose(const unsigned char *sha1, time_t mtime);
/* global flag to enable extra checks when accessing packed objects */
extern int do_check_packed_object_crc;
+/* for development: log offset of pack access */
+extern const char *log_pack_access;
+
extern int check_sha1_signature(const unsigned char *sha1, void *buf, unsigned long size, const char *type);
extern int move_temp_to_file(const char *tmpfile, const char *filename);