From: Chris Friesen <cfriesen@nortelnetworks.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 16:39:42 -0400 [thread overview]
Message-ID: <3E9B1C8E.5030707@nortelnetworks.com> (raw)
In-Reply-To: b7etcd$s0n$1@cesium.transmeta.com
H. Peter Anvin wrote:
> Followup to: <11640000.1050332688@[10.10.2.4]> By author: "Martin J.
> Bligh" <mbligh@aracnet.com> In newsgroup: linux.dev.kernel
>
>>> Martin, something which was not mentioned last week (I've just checked).
>>>
>>> It's OK if we never write to disk unless explicitely told, but will we
>>> writeback when we munmap?
> munmap() and fsync() or msync() will flush it to disk; there is no reason
> munmap() should unless perhaps the file was opened O_SYNC.
Wait a minute. Shouldn't a file opened O_SYNC flush the writes as they happen,
removing the requirement for any explicit syncing? If it doesn't there are some
very broken apps around.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-04-14 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 3:57 Memory mapped files question Bryan Shumsky
2003-04-14 14:36 ` Martin J. Bligh
2003-04-14 15:07 ` Antonio Vargas
2003-04-14 15:04 ` Martin J. Bligh
2003-04-14 18:07 ` H. Peter Anvin
2003-04-14 20:39 ` Chris Friesen [this message]
2003-04-14 21:12 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:31 Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky
2003-04-14 19:53 ` Alan Cox
2003-04-14 21:24 ` Chris Friesen
2003-04-14 20:13 ` Richard B. Johnson
2003-04-14 20:27 ` Frank van Maarseveen
2003-04-14 20:52 ` Richard B. Johnson
2003-04-14 22:08 ` H. Peter Anvin
2003-04-15 4:56 ` Jamie Lokier
2003-04-15 5:30 ` H. Peter Anvin
2003-04-14 19:50 Perez-Gonzalez, Inaky
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=3E9B1C8E.5030707@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=hpa@zytor.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