From: Linus Torvalds <torvalds@linux-foundation.org>
To: "epankala@cc.hut.fi" <epankala@cc.hut.fi>
Cc: git@vger.kernel.org
Subject: Re: GIT max file size.
Date: Thu, 8 May 2008 13:46:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805081334530.2940@woody.linux-foundation.org> (raw)
In-Reply-To: <48232B48.9010900@cc.hut.fi>
On Thu, 8 May 2008, epankala@cc.hut.fi wrote:
>
> I received "fatal: Out of memory, malloc failed" error when I tried to
> check in file of ~2.5G
There's two issues there.
One is that a lot of what git does is simply "whole file at a time". The
diff machinery, and a lot of the core stuff, simply just expects to be
able to mmap() or read the whole file in one go. So on a 32-bit
architecture, you'll generally be limited to the size of the address
space, not to anything else.
The other thing is then that (partly because of the above) there probably
are places where we haven't been as careful about size-type things as we
could have been. A lot of the code uses size_t, but I bet not everything
does.
Linus
prev parent reply other threads:[~2008-05-08 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 16:33 GIT max file size epankala
2008-05-08 18:46 ` Alex Riesen
2008-05-08 20:46 ` 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.1.10.0805081334530.2940@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=epankala@cc.hut.fi \
--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;
as well as URLs for NNTP newsgroup(s).