From: Linus Torvalds <torvalds@linux-foundation.org>
To: Emmanuel Puerto <emmanuel.puerto@maxim-ic.com>
Cc: Jeff King <peff@peff.net>, "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: [BUG] malloc error when using large file.
Date: Tue, 23 Jun 2009 14:15:21 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906231412070.3240@localhost.localdomain> (raw)
In-Reply-To: <B03A893ADFE80748942D13AFAF2845190C2D5D3BDC@ITSVLEX06.it.maxim-ic.internal>
On Tue, 23 Jun 2009, Emmanuel Puerto wrote:
>
>
> > Many operations in git assume that a whole file can be held in memory at
> > once. Do you actually have 2G available on the machine? Are there any OS
> > limits that might be a problem?
>
> Thanks for your answer Jeff,
>
> Yes I have more that 2 Go available when a do it, and after this
> allocation error if I try to do a 'git add' with a 9Go file, I did not
> have any issue.
Can you add the 2GB files individually, using
for i in All-f00?.vmdk; do git add $i; done
or similar?
It does sound like an unlucky malloc VM space fragmentation issue,
although since the files you add are the same size I'd have not really
expected that with any normal malloc library. But with some mixed small
and large allocations, I could imagine that the fragmentation happens, and
you end up having huge areas that aren't _quite_ useful for the next file
due to having some small allocation taking part of it.
Linus
next prev parent reply other threads:[~2009-06-23 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 9:54 [BUG] malloc error when using large file Emmanuel Puerto
2009-06-22 21:15 ` Jeff King
2009-06-23 7:05 ` Emmanuel Puerto
2009-06-23 18:42 ` Jeff King
2009-06-23 21:15 ` Linus Torvalds [this message]
2009-06-24 8:35 ` Emmanuel Puerto
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.2.01.0906231412070.3240@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=emmanuel.puerto@maxim-ic.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).