From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bryan Shumsky <bzs@via.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Memory mapped files question
Date: Mon, 14 Apr 2003 17:24:38 -0400 [thread overview]
Message-ID: <3E9B2716.6030503@nortelnetworks.com> (raw)
In-Reply-To: 1050349977.26521.2.camel@dhcp22.swansea.linux.org.uk
Alan Cox wrote:
> On Llu, 2003-04-14 at 20:42, Bryan Shumsky wrote:
>
>>Rewriting all of our code to manually handle the flushing is a MAJOR
>>undertaking, so I was hoping there might be some sneaky solution you could
>>come up with. Any ideas?
>>
>
> Create a thread that does msync's every so often. Its that simple
How do you deal with ensuring (or even trying to ensure) that the stuff *on
disk* is sane?
If I understand correctly, msync() doesn't guarantee order of writes, so
randomly firing off msync() calls doesn't help.
If I want to update an entry and then set a flag saying that the entry is
correct, I need to have two msyncs, one for the entry data, and one for the
flag. I had hoped that I could avoid this by opening the file with O_SYNC, but
hpa just disabused me of that notion...
Are the mmap semantics different for devices?
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 21:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 19:31 Memory mapped files question Perez-Gonzalez, Inaky
2003-04-14 19:42 ` Bryan Shumsky
2003-04-14 19:53 ` Alan Cox
2003-04-14 21:24 ` Chris Friesen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:50 Perez-Gonzalez, Inaky
2003-04-14 3:57 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
2003-04-14 21:12 ` H. Peter Anvin
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=3E9B2716.6030503@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzs@via.com \
--cc=inaky.perez-gonzalez@intel.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