From: Goswin von Brederlow <goswin-v-b@web.de>
To: "Richard W.M. Jones" <rich@annexia.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] appending data to a mmap-ed file
Date: Fri, 17 Dec 2010 20:05:21 +0100 [thread overview]
Message-ID: <871v5gte32.fsf@frosties.localnet> (raw)
In-Reply-To: <20101217144850.GC3647@annexia.org> (Richard W. M. Jones's message of "Fri, 17 Dec 2010 14:48:50 +0000")
"Richard W.M. Jones" <rich@annexia.org> writes:
> On Fri, Dec 17, 2010 at 01:36:35AM +0100, Goswin von Brederlow wrote:
>> Or avoid the whole issue and make the file large enough to begin
>> with. Thanks to sparse files you can create a huge file that only uses 1
>> block on disk. Then you can mmap that and it will use up more disk space
>> as you fill in data automatically.
>
> Sure, if you have an upper limit. Neither works well on 32 bit
> architectures where you're really limited for contiguous free address
> space.
>
> Rich.
Which has nothing to do with appending to a mmap-ed file. You are
already in trouble if the file too big to begin with.
If you need more than 1-3GB mapped on 32bit then you need to map it
dynamically in chunks as needed, which gets a hell of a lot more
complex. Frankly at that point I would just buy a 64bit cpu or install a
64bit kernel on the one you have.
MfG
Goswin
next prev parent reply other threads:[~2010-12-17 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:31 Joel Reymont
2010-12-16 12:38 ` [Caml-list] " Jesper Louis Andersen
2010-12-16 13:13 ` Joel Reymont
2010-12-16 12:57 ` Gerd Stolpmann
2010-12-16 17:16 ` Richard W.M. Jones
2010-12-17 0:36 ` Goswin von Brederlow
2010-12-17 14:48 ` Richard W.M. Jones
2010-12-17 15:49 ` Joel Reymont
2010-12-17 19:05 ` Goswin von Brederlow [this message]
2010-12-18 9:56 ` Christophe Raffalli
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=871v5gte32.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=caml-list@yquem.inria.fr \
--cc=rich@annexia.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).