From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mmap
Date: Mon, 3 Nov 2008 01:22:35 +0100 [thread overview]
Message-ID: <20081103002235.GD27416@nibiru.local> (raw)
In-Reply-To: <1217432588.5036.100.camel@goose.sun.com>
* Roman V. Shaposhnik <rvs@sun.com> wrote:
> On Wed, 2008-07-30 at 17:29 +0200, Enrico Weigelt wrote:
> > Convenience is one point (sometimes be a big point), but another
> > important one is sharing. Without mmap(), an (real) shared library
> > support most likely will require special kernel support.
>
> What aspect of shared libraries are you aching for? Dynamic
> linking or the dynamic loading?
3rd: Sharing pages.
Well, this perhaps also could be done if the kernel would be able
to detect equal pages and automatically map them together (maybe
w/ copy-on-write again).
BTW mmap() is also nice for creating shared memory between
(local) processes. For example RDBMS'es can get a huge benetit
from this.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
cellphone: +49 174 7066481 email: info@metux.de skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2008-11-03 0:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 14:24 mmap Russ Cox
2008-07-17 14:34 ` [9fans] mmap erik quanstrom
2008-07-29 8:52 ` Enrico Weigelt
2008-07-29 9:45 ` Charles Forsyth
2008-07-29 15:04 ` Alexander Sychev
2008-07-29 15:19 ` erik quanstrom
2008-07-29 15:35 ` ron minnich
2008-07-29 15:46 ` Roman V. Shaposhnik
2008-07-29 15:35 ` David Leimbach
2008-07-29 16:28 ` Venkatesh Srinivas
2008-07-29 16:55 ` Charles Forsyth
2008-07-29 17:08 ` Charles Forsyth
2008-07-30 16:36 ` Roman V. Shaposhnik
2008-07-30 17:02 ` Paul Lalonde
2008-07-31 21:39 ` Charles Forsyth
2008-07-31 23:19 ` Bakul Shah
2008-08-01 0:32 ` ron minnich
2008-08-01 3:18 ` David Leimbach
2008-08-02 13:22 ` Richard Miller
2008-08-02 16:10 ` ron minnich
2008-08-02 19:12 ` Richard Miller
2008-07-31 8:51 ` Paweł Lasek
[not found] ` <20080729162639.GA31092@satori.no-ip.org>
2008-07-30 15:29 ` Enrico Weigelt
2008-07-30 15:43 ` Roman V. Shaposhnik
2008-11-03 0:22 ` Enrico Weigelt [this message]
2008-07-30 16:25 ` Joel C. Salomon
2008-07-30 17:28 ` Kernel Panic
2008-07-30 18:26 ` erik quanstrom
2008-07-31 1:42 ` Joel C. Salomon
2008-11-03 0:50 erik quanstrom
2008-11-03 1:36 ` ron minnich
2008-11-03 6:29 ` Charles Forsyth
2008-11-03 6:58 ` ron minnich
2008-11-03 7:50 ` Bruce Ellis
2008-11-04 4:43 ` Enrico Weigelt
2008-11-04 7:15 ` Andrew Simmons
2008-11-04 8:01 ` Bakul Shah
2008-11-04 14:13 ` Charles Forsyth
2008-11-10 23:15 ` gas
2008-11-04 16:02 ` ron minnich
2008-11-04 18:19 ` Kim Shrier
2008-11-04 16:09 ` David Leimbach
[not found] <1d371286c515cad580f68eddbe2cdf57@quanstro.net>
2008-11-03 3:18 ` Enrico Weigelt
2008-11-03 3:31 ` ron minnich
2008-11-03 6:27 ` Charles Forsyth
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=20081103002235.GD27416@nibiru.local \
--to=weigelt@metux.de \
--cc=9fans@9fans.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).