From: Dennis Heuer <dh@triple-media.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: how to best map/buffer a file to memory by being able to lock sequences thread-safe
Date: Mon, 15 Oct 2007 17:46:35 +0200 [thread overview]
Message-ID: <20071015174635.4cae245c.dh@triple-media.com> (raw)
In-Reply-To: <20071013000158.d011bc82.dh@triple-media.com>
i did not try obstacks yet, will have a look at them. what bothers me
at the moment is that mremap() is not a standard and that it operates
strangely to me:
ENOMEM
The region is private writable, and insufficient virtual memory is
available to extend it. Also, this error will occur if MREMAP_MAYMOVE
is not given and the extension would collide with another mapped region.
i thought that mmap'ed space is only virtually aligned. possibly it's
better to write buffers oneself? the posix interfaces look strange to
me. they seem halfhearted and weirdly incompatible. consider a file
that is growing. how to best remap it?
regards,
dennis heuer
next prev parent reply other threads:[~2007-10-15 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 22:01 how to best map/buffer a file to memory by being able to lock sequences thread-safe Dennis Heuer
2007-10-13 16:00 ` Glynn Clements
2007-10-15 15:46 ` Dennis Heuer [this message]
2007-10-16 10:54 ` Glynn Clements
2007-10-16 17:28 ` Dennis Heuer
2007-10-16 18:44 ` Glynn Clements
2007-10-17 14:42 ` Bryan Christ
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=20071015174635.4cae245c.dh@triple-media.com \
--to=dh@triple-media.com \
--cc=linux-c-programming@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).