Date: Sat, 10 Feb 2001 11:32:48 -0800 (PST) From: Richard Hodges <rh@matriplex.com> To: Nik Clayton <nik@FreeBSD.ORG> Cc: hackers@FreeBSD.ORG Subject: Re: Updating mmap(2) [nik@freebsd.org: Re: pipe] Message-ID: <Pine.BSF.4.10.10102101115450.79449-100000@mail.matriplex.com> In-Reply-To: <20010210151055.A99274@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Feb 2001, Nik Clayton wrote:
> There was no comment to these. Any objections if I commit my proposed
> changes?
> mmap - map files or devices into memory
>
> [...]
>
> doesn't immediately shout "You can use this function to allocate memory
> as well".
>
> Perhaps
>
> mmap - allocate memory, or map files or devices into memory
>
> would be better?
You have my vote. That information would have saved me quite a few
hours of angst a few years ago when I was looking for a way to share
memory between processes. In fact, it will probably be an important
tool for me for some time to come. In one case, using threads (instead
of processes) with a decent amount of I/O increases load by about 20%.
While you're at it :-) maybe you could add a few lines suggesting that
with the MAP_SHARED flag, this is a useful method of sharing memory
between processes.
> In addition, mmap isn't listed in the SEE ALSO for malloc(3), nor is it
> listed in memory(3). mmap() is listed in malloc(3), but only in an
> error message.
Sounds good to me.
-Richard
-------------------------------------------
Richard Hodges | Matriplex, inc.
<title> | 769 Basque Way
rh@matriplex.com | Carson City, NV 89706
775-886-6477 | www.matriplex.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10102101115450.79449-100000>