From: "J . A . Magallon" <jamagallon@able.es>
To: Jerry Hong <jhong001@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how mmap() works?
Date: Fri, 30 Mar 2001 00:38:01 +0200 [thread overview]
Message-ID: <20010330003801.E1052@werewolf.able.es> (raw)
In-Reply-To: <20010329221451.27582.qmail@web4303.mail.yahoo.com>
In-Reply-To: <20010329221451.27582.qmail@web4303.mail.yahoo.com>; from jhong001@yahoo.com on Fri, Mar 30, 2001 at 00:14:51 +0200
On 03.30 Jerry Hong wrote:
> Hi,
> mmap() creates a mmaped memory associated with a
> physical file. If a process updates the mmaped memory,
> Linux will updates the file "automatically". If this
> is the case, why do we need msync()? If this is not
Where did you heard that ?
man mmap(2):
..
MAP_SHARED Share this mapping with all other processes
that map this object. Storing to the region is
equivalent to writing to the file. The file
may not actually be updated until msync(2) or
munmap(2) are called.
..
man msync(2):
..
DESCRIPTION
msync flushes changes made to the in-core copy of a file
that was mapped into memory using mmap(2) back to disk.
Without use of this call there is no guarantee that
changes are written back before munmap(2) is called. To
.
--
J.A. Magallon # Let the source
mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.2-ac28 #1 SMP Thu Mar 29 16:41:17 CEST 2001 i686
next prev parent reply other threads:[~2001-03-29 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 22:14 how mmap() works? Jerry Hong
2001-03-29 22:38 ` J . A . Magallon [this message]
2001-04-01 16:41 ` Andreas Bombe
2001-04-01 20:28 ` Tim Hockin
2001-04-02 0:42 ` Andreas Bombe
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=20010330003801.E1052@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jhong001@yahoo.com \
--cc=linux-kernel@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