author | René Scharfe <rene.scharfe@lsrfire.ath.cx> | |
Mon, 24 Oct 2011 21:59:14 +0000 (23:59 +0200) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 26 Oct 2011 22:25:59 +0000 (15:25 -0700) | ||
commit | debed2a6291a29fd7b0e96f63fbf0142ed3280eb | |
tree | 89aac247843d0ca266dcf854bf656976189281f8 | tree | snapshot |
parent | 10b2a48113b8ab6b8f48229eb40fc3637ce025ae | commit | diff |
read-cache.c: allocate index entries individually
The code to estimate the in-memory size of the index based on its on-disk
representation is subtly wrong for certain architecture-dependent struct
layouts. Instead of fixing it, replace the code to keep the index entries
in a single large block of memory and allocate each entry separately
instead. This is both simpler and more flexible, as individual entries
can now be freed. Actually using that added flexibility is left for a
later patch.
Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The code to estimate the in-memory size of the index based on its on-disk
representation is subtly wrong for certain architecture-dependent struct
layouts. Instead of fixing it, replace the code to keep the index entries
in a single large block of memory and allocate each entry separately
instead. This is both simpler and more flexible, as individual entries
can now be freed. Actually using that added flexibility is left for a
later patch.
Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
cache.h | diff | blob | history | |
read-cache.c | diff | blob | history |