From: Linus Torvalds <torvalds@linux-foundation.org>
To: Brian Downing <bdowning@lavos.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Dynamic window size on repack?
Date: Sun, 8 Jul 2007 14:39:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707081437590.31544@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707081429500.31544@woody.linux-foundation.org>
On Sun, 8 Jul 2007, Linus Torvalds wrote:
>
> In other words, just look at how the variables "struct unpacked *array"
> (the whole window array) and the "struct unpacked *n" (the "next entry" in
> the array using a simple circular queue using "idx") are accessed.
Side note: a limit based on object sizes is likely a much better way to
handle the window than just a "number of objects" thing ever was. Doing
the size in number of objects was easier, and is fine for source code that
tends to have a reasonably normal distribution of sized, but yeah, if you
have a few really big objects with lots of history, then it's likely the
wrong thing to do just because it can get really expensive.
Linus
prev parent reply other threads:[~2007-07-08 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 21:16 [RFC] Dynamic window size on repack? Brian Downing
2007-07-08 21:35 ` Dana How
2007-07-08 21:35 ` Linus Torvalds
2007-07-08 21:39 ` Linus Torvalds [this message]
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=alpine.LFD.0.999.0707081437590.31544@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=bdowning@lavos.net \
--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