From: Kjetil Barvik <barvik@broadpark.no>
To: git@vger.kernel.org
Cc: Kjetil Barvik <barvik@broadpark.no>
Subject: [PATCH v10 0/5] git checkout: optimise away lots of lstat() calls
Date: Sun, 18 Jan 2009 16:14:49 +0100 [thread overview]
Message-ID: <1232291694-18083-1-git-send-email-barvik@broadpark.no> (raw)
Changes since version 9
--- patch 1/5 ---
bug fix (missed optimisation):
If we have track_flags = FL_SYMLINK|FL_DIR, and:
cache => A/B/C/D/S (a symlink)
name => A/B/C (a directory)
The cache would return with a (cached) FL_DIR result as expected,
_but_ it would set the cache to "A/B/C", so we lose some information.
--- patch 4/5 ---
bug fix: if we get a match from the cache for the name to invalidate,
we reset the cache if we are not allowed to track directories (inside
the invalidate_lstat_cache() function).
Kjetil Barvik (5):
lstat_cache(): more cache effective symlink/directory detection
lstat_cache(): introduce has_symlink_or_noent_leading_path() function
lstat_cache(): introduce has_dirs_only_path() function
lstat_cache(): introduce invalidate_lstat_cache() function
lstat_cache(): introduce clear_lstat_cache() function
cache.h | 4 +
entry.c | 34 +++-----
symlinks.c | 263 ++++++++++++++++++++++++++++++++++++++++++++++---------
unpack-trees.c | 4 +-
4 files changed, 238 insertions(+), 67 deletions(-)
next reply other threads:[~2009-01-18 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 15:14 Kjetil Barvik [this message]
2009-01-18 15:14 ` [PATCH v10 1/5] lstat_cache(): more cache effective symlink/directory detection Kjetil Barvik
2009-01-18 15:14 ` [PATCH v10 2/5] lstat_cache(): introduce has_symlink_or_noent_leading_path() function Kjetil Barvik
2009-01-18 15:14 ` [PATCH v10 3/5] lstat_cache(): introduce has_dirs_only_path() function Kjetil Barvik
2009-01-18 15:14 ` [PATCH v10 4/5] lstat_cache(): introduce invalidate_lstat_cache() function Kjetil Barvik
2009-01-18 15:14 ` [PATCH v10 5/5] lstat_cache(): introduce clear_lstat_cache() function Kjetil Barvik
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=1232291694-18083-1-git-send-email-barvik@broadpark.no \
--to=barvik@broadpark.no \
--cc=git@vger.kernel.org \
/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).