From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 4/5] archive-tar: stream large blobs to tar file
Date: Tue, 01 May 2012 00:12:00 +0200 [thread overview]
Message-ID: <4F9F0E30.70403@lsrfire.ath.cx> (raw)
In-Reply-To: <7vhaw0ewb8.fsf@alter.siamese.dyndns.org>
Am 30.04.2012 23:36, schrieb Junio C Hamano:
> René Scharfe<rene.scharfe@lsrfire.ath.cx> writes:
>
>>> +static int stream_blob_to_file(const unsigned char *sha1)
>>> +{
>>> + struct git_istream *st;
>>> + enum object_type type;
>>> + unsigned long sz;
>>> +
>>> + st = open_istream(sha1,&type,&sz, NULL);
>>> + if (!st)
>>> + return error("cannot stream blob %s", sha1_to_hex(sha1));
>>> + for (;;) {
>>> + char buf[BLOCKSIZE];
>>> + ssize_t readlen;
>>> +
>>> + readlen = read_istream(st, buf, sizeof(buf));
>>> +
>>> + if (readlen<= 0)
>>> + return readlen;
>>> + write_blocked(buf, readlen);
>>> + }
>>> + close_istream(st);
>>> + return 0;
>>> +}
>>
>> The stream is never closed. Perhaps squash this in?
>>
>> diff --git a/archive-tar.c b/archive-tar.c
>> index 506c8cb..6109fd3 100644
>> --- a/archive-tar.c
>> +++ b/archive-tar.c
>> @@ -66,6 +66,7 @@ static void write_blocked(const void *data, unsigned long size)
>> static int stream_blob_to_file(const unsigned char *sha1)
>> {
>> struct git_istream *st;
>> + ssize_t readlen;
>> enum object_type type;
>> unsigned long sz;
>>
>> @@ -74,16 +75,15 @@ static int stream_blob_to_file(const unsigned char *sha1)
>> return error("cannot stream blob %s", sha1_to_hex(sha1));
>> for (;;) {
>> char buf[BLOCKSIZE];
>> - ssize_t readlen;
>>
>> readlen = read_istream(st, buf, sizeof(buf));
>>
>> if (readlen<= 0)
>> - return readlen;
>> + break;
>> write_blocked(buf, readlen);
>> }
>> close_istream(st);
>> - return 0;
>> + return readlen;
>> }
>
> Your patch on top obviouly is the right thing to do, but reading the code
> again, I am not sure if the original is correct. read_istream() itself
> does not promise that it will always fill the buffer before returning (it
> could return with a short read). It seems incorrect that the caller does
> not loop to avoid padding a short read with padding by calling
> write_blocked().
Yes, indeed, good catch. It could also write to block directly and
avoid copying the buffer again. The tail clearing part of
write_blocked() can certainly be reused, but the rest will probably have
to be reimplemented around read_istream().
René
next prev parent reply other threads:[~2012-04-30 22:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 4:57 [PATCH 0/5] Large file support for git-archive Nguyễn Thái Ngọc Duy
2012-04-30 4:57 ` [PATCH 1/5] archive-tar: turn write_tar_entry into blob-writing only Nguyễn Thái Ngọc Duy
2012-04-30 18:15 ` Junio C Hamano
2012-04-30 22:11 ` René Scharfe
2012-04-30 4:57 ` [PATCH 2/5] archive-tar: unindent write_tar_entry by one level Nguyễn Thái Ngọc Duy
2012-04-30 4:57 ` [PATCH 3/5] archive: delegate blob reading to backend Nguyễn Thái Ngọc Duy
2012-04-30 21:07 ` René Scharfe
2012-04-30 4:57 ` [PATCH 4/5] archive-tar: stream large blobs to tar file Nguyễn Thái Ngọc Duy
2012-04-30 19:01 ` Junio C Hamano
2012-04-30 21:08 ` René Scharfe
2012-04-30 21:36 ` Junio C Hamano
2012-04-30 22:12 ` René Scharfe [this message]
2012-04-30 4:57 ` [PATCH 5/5] archive-zip: stream large blobs into zip file Nguyễn Thái Ngọc Duy
2012-04-30 19:12 ` Junio C Hamano
2012-04-30 22:54 ` René Scharfe
2012-04-30 22:11 ` [PATCH 5a/5] streaming: void pointer instead of char pointer René Scharfe
2012-04-30 22:12 ` [PATCH 6a/5] archive-zip: remove uncompressed_size René Scharfe
2012-04-30 22:12 ` [PATCH 7a/5] archive-zip: factor out helpers for writing sizes and CRC René Scharfe
2012-04-30 22:12 ` [PATCH 8a/5] archive-zip: streaming for stored files René Scharfe
2012-04-30 22:12 ` [PATCH 9a/5] archive-zip: streaming for deflated files René Scharfe
2012-04-30 19:15 ` [PATCH 0/5] Large file support for git-archive Junio C Hamano
2012-04-30 21:07 ` René Scharfe
2012-05-01 10:19 ` Nguyen Thai Ngoc Duy
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=4F9F0E30.70403@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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).