Messages in this thread | | | Date | Mon, 14 Apr 2003 17:24:38 -0400 | From | Chris Friesen <> | Subject | Re: Memory mapped files question |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |