From: Stas Sergeev <stsp@aknet.ru>
To: William Tambe <tambewilliam@gmail.com>
Cc: Hugh Dickins <hugh@veritas.com>, linux-kernel@vger.kernel.org
Subject: Re: Concerning a post that you made about expandable anonymous shared mappings
Date: Mon, 02 Jul 2007 22:21:34 +0400 [thread overview]
Message-ID: <4689422E.5040503@aknet.ru> (raw)
In-Reply-To: <4689375C.2090505@gmail.com>
Hello.
William Tambe wrote:
> And it just doesn't make sens to have mmap() map ANONYMOUS shared memory
> and mremap() not to expand it and make the expanded area available.
I agree with this, but the argument against
that approach was that then you can only
enlarge the backing-store, but never shrink.
I personally think it is a valid argument,
even though the problem is probably not very
important.
Also, you can't expand the SysV SHM with mremap
just as well - it will give you a SIGBUS too IIRC.
So for that discussion of 2004, I lost the
battle and was convinced that the proposed
approach is not very good...
> Would you happen to know how I can work around that issue for now, and
> make writing in an expended area not to generate a Bus error?
Have you tried the Posix SHM instead? It works
very well for me. Back in 2004 the glibc had
bugs, so I couldn't easily use posix shm and
was thinking about the different approaches.
But now it should suffice.
next prev parent reply other threads:[~2007-07-02 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 19:52 Concerning a post that you made about expandable anonymous shared mappings William Tambe
2007-07-02 15:33 ` Hugh Dickins
2007-07-02 17:35 ` William Tambe
2007-07-02 18:21 ` Stas Sergeev [this message]
2007-07-02 18:10 ` Stas Sergeev
2007-07-03 15:48 ` Hugh Dickins
2007-07-03 18:29 ` Stas Sergeev
2007-07-10 1:50 ` William Tambe
2007-07-10 20:10 ` Hugh Dickins
2007-07-10 20:55 ` William Tambe
2007-07-11 4:12 ` Stas Sergeev
2007-07-12 6:35 ` William Tambe
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=4689422E.5040503@aknet.ru \
--to=stsp@aknet.ru \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tambewilliam@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.