From: Kjetil Barvik <barvik@broadpark.no>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Kjetil Barvik <barvik@broadpark.no>
Subject: [PATCH/RFC v2 0/3] git checkout optimisation - part 3
Date: Thu, 19 Feb 2009 21:08:27 +0100 [thread overview]
Message-ID: <cover.1235071656.git.barvik@broadpark.no> (raw)
Changes sine v1
(v1 was posted with subject "The ext4 filesystem and racy git")
-- patch 2/3 --
Added missing timestamp => timestamp.(u)sec update for
unpack-trees.c
-- patch 3/3 --
New patch which removes some 14300 lstat(2) calls, and the total is
now at 41677 calls, or 1.382 calls/unique string to lstat() for the
reference 'git checkout'-test to Linux tag v2.6.27.
Total reduction so far for all the lstat/git checkout optimisation
patches has been 120954 - 41677 = 79277 calls. Some 14400 fstat(2)
calls is added, but those should be faster than simmilar lstat()
calls.
(patch-series based on master)
Kjetil Barvik (3):
fix compile error when USE_NSEC is defined
make USE_NSEC work as expected
verify_uptodate(): add ce_uptodate(ce) test
builtin-fetch-pack.c | 4 +-
cache.h | 6 ++--
read-cache.c | 70 ++++++++++++++++++++++++++++++++++++++++----------
unpack-trees.c | 10 +++++--
4 files changed, 68 insertions(+), 22 deletions(-)
next reply other threads:[~2009-02-19 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 20:08 Kjetil Barvik [this message]
2009-02-19 20:08 ` [PATCH/RFC v2 1/3] fix compile error when USE_NSEC is defined Kjetil Barvik
2009-02-19 20:08 ` [PATCH/RFC v2 2/3] make USE_NSEC work as expected Kjetil Barvik
2009-02-20 8:35 ` Junio C Hamano
2009-02-20 10:07 ` Kjetil Barvik
2009-02-21 5:42 ` Junio C Hamano
2009-02-19 20:08 ` [PATCH/RFC v2 3/3] verify_uptodate(): add ce_uptodate(ce) test Kjetil Barvik
2009-02-20 8:35 ` [PATCH/RFC v2 0/3] git checkout optimisation - part 3 Junio C Hamano
2009-02-20 9:03 ` Kjetil Barvik
2009-02-20 9:26 ` Sverre Rabbelier
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=cover.1235071656.git.barvik@broadpark.no \
--to=barvik@broadpark.no \
--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.
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 NNTP newsgroup(s).