From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/5] autoconf: Preliminary check for working mmap
Date: Tue, 5 Sep 2006 02:25:31 -0400 [thread overview]
Message-ID: <20060905062531.GA30496@spearce.org> (raw)
In-Reply-To: <7vu03mkiei.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> > I'm maybe only 1/3 of the way through the sliding window mmap
> > implementation. I've got a good chunk of sha1_file.c converted but I
> > still have to deal with the copying in pack-objects.c and the verify
> > code in verify-pack.c. I'm hoping I can send a preliminary patch
> > series tomorrow as I'm going to work on it more tonight and tomorrow.
>
> Thanks -- I was tempted to do this myself after finishing the
> index_64 change in "pu" branch, but have resisted the temptation
> myself so far. Being lazy, the less I have to code the better,
> naturally ;-).
I thought that might be the case. I should be able to finish it
up tomorrow. :-)
I don't know if I've made this more complex than I really need to
but I've permitted multiple windows per pack. There is just one
LRU of all windows across all packs and a maximum amount of address
space to use for pack mappings. Least recently used window gets
tossed when we need a different window. This permits us to keep
say a window active on the front of a pack (near the commits) and
another different active window closer to the back (near the blobs).
That multiple window feature made it a slightly non-trivial copy
and paste from fast-import but I think its worth it for tree walking
type applications.
--
Shawn.
next prev parent reply other threads:[~2006-09-05 7:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 22:54 [PATCH 0/5] Some autoconf patches Jakub Narebski
2006-09-04 22:55 ` [PATCH 1/5] autoconf: Add some commented out variables to config.mak.in Jakub Narebski
2006-09-04 22:55 ` [PATCH 2/5] autoconf: Add -liconv to LIBS when NEEDS_LIBICONV Jakub Narebski
2006-09-05 16:25 ` Jonas Fonseca
2006-09-05 20:03 ` [PATCH] autoconf: Fix copy'n'paste error Jakub Narebski
2006-09-05 21:27 ` [PATCH 2/5] autoconf: Add -liconv to LIBS when NEEDS_LIBICONV Junio C Hamano
2006-09-04 22:56 ` [PATCH 3/5] autoconf: Preliminary check for working mmap Jakub Narebski
2006-09-04 23:36 ` Junio C Hamano
2006-09-04 23:43 ` Jakub Narebski
2006-09-05 3:09 ` Shawn Pearce
2006-09-05 5:10 ` Junio C Hamano
2006-09-05 6:25 ` Shawn Pearce [this message]
2006-09-05 7:43 ` Junio C Hamano
2006-09-06 3:40 ` Shawn Pearce
2006-09-06 7:17 ` Junio C Hamano
2006-09-06 8:15 ` Junio C Hamano
2006-09-07 5:58 ` Shawn Pearce
2006-09-04 22:57 ` [PATCH 4/5] autoconf: Check for subprocess.py Jakub Narebski
2006-09-04 22:58 ` [PATCH 5/5] autoconf: Quote AC_CACHE_CHECK arguments Jakub Narebski
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=20060905062531.GA30496@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).