From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: fact-import: failed to apply delta
Date: Tue, 10 Feb 2009 15:15:09 -0800 [thread overview]
Message-ID: <7vtz71khoi.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090210230950.GX30949@spearce.org> (Shawn O. Pearce's message of "Tue, 10 Feb 2009 15:09:50 -0800")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> What more can I really say here other than maybe this?
>
> diff --git a/fast-import.c b/fast-import.c
> index 03b13e0..7bfb563 100644
> --- a/fast-import.c
> +++ b/fast-import.c
> @@ -1204,6 +1204,12 @@ static void *gfi_unpack_entry(
> */
> p->pack_size = pack_size + 20;
> }
> + /* DANGER, WILL ROBINSON DANGER !!!!
> + *
> + * unpack_entry() wasn't meant to be called the way we are
> + * about to call it right here. Be very careful, any sort
> + * of assumption is probably wrong.
> + */
> return unpack_entry(p, oe->offset, &type, sizep);
> }
Yuck ;-).
>> By the way, strictly speaking, you need to release the delta_base_cache
>> entries that is based on pack_data and nothing else, no?
>
> Right.
>
> But the hiccup of a checkpoint in terms of overall performance is
> such a huge amount (due to needing to re-read the entire pack to
> compute its final checksum) that the loss of the delta_base_cache
> is pretty much a drop in the bucket here.
>
> I can go back and add in a struct packed_git* and filter to only
> those entries in the cache, but it doesn't seem worth it to me.
Nah, that was not a suggestion but a question.
The patch can and should go to maint, right?
next prev parent reply other threads:[~2009-02-10 23:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 3:26 fact-import: failed to apply delta Daniel Barkalow
2009-02-10 10:28 ` Johannes Schindelin
2009-02-10 15:56 ` Shawn O. Pearce
2009-02-10 17:15 ` Daniel Barkalow
2009-02-10 17:22 ` Shawn O. Pearce
2009-02-10 17:47 ` Daniel Barkalow
2009-02-10 19:12 ` Shawn O. Pearce
2009-02-10 20:03 ` Daniel Barkalow
2009-02-10 20:12 ` Shawn O. Pearce
2009-02-10 21:19 ` Daniel Barkalow
2009-02-10 21:25 ` Shawn O. Pearce
2009-02-10 21:32 ` Daniel Barkalow
2009-02-10 21:36 ` Shawn O. Pearce
2009-02-10 21:51 ` Daniel Barkalow
2009-02-10 22:30 ` Junio C Hamano
2009-02-10 22:47 ` Junio C Hamano
2009-02-10 23:09 ` Shawn O. Pearce
2009-02-10 23:15 ` Junio C Hamano [this message]
2009-02-10 23:16 ` Shawn O. Pearce
2009-02-10 23:32 ` Junio C Hamano
2009-02-11 18:09 ` Daniel Barkalow
2009-02-11 18:15 ` Shawn O. Pearce
2009-02-11 18:30 ` Junio C Hamano
2009-02-11 18:33 ` Daniel Barkalow
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=7vtz71khoi.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.