> Miklos Szeredi wrote: > >>>> This still does not address the situation where a file is 'permanently' > >>>> mmap'd, does it? > >>>> > >>> So? If application doesn't do msync, then the file times won't be > >>> updated. That's allowed by the standard, and so portable applications > >>> will have to call msync. > >>> > >> It is allowed, but it is clearly not useful behaviour. Nowhere is it set > >> in stone that we should be implementing just the minimum allowed. > >> > > > > You're right. In theory, at least. But in practice I don't think > > this matters. Show me an application that writes to a shared mapping > > then doesn't call either msync or munmap and doesn't even exit. > > > > If there were lot of these apps, then this bug would have been fixed > > lots of years earlier. In fact there are _very_ few apps writing to > > shared mappings at all. > > > > > > Perhaps true, although I know of at least one customer of Red Hat who > does have an application (or more) than uses mmap'd files and is > suffering from this lack of appropriate semantics. They are not > getting files backed up which need to be. Yeah, but I bet, that just updating the times on msync and munmap will cure the problem. Until you prove me wrong, this is a purely theoretical argument. > > Applications should be encouraged to call msync(MS_ASYNC) because: > > > > - it's very fast (basically a no-op) on recent linux kernels > > > > - it's the only portable way to guarantee, that the data you written > > will _ever_ hit the disk. > > > > There's really no downside to using msync(MS_ASYNC) in your > > application, so making an effort to support applications that don't do > > this is stupid, IMO. > > It may be a no-op on recent Linux kernels, but I don't think that it > is a no-op on other systems. Exactly. Which is the reason applications _have_ to call msync on these OSs if they want data to be synchronized with the file. There are two cases: 1) app don't cares about it's data being synchronized with the file 2) app does care In the first case there's no problem if the times aren't updated, since the app didn't care. In the second case the a portable application has to call msync, and on linux it doesn't even lose any performance from this, so it should be happy. You are trying to provide for an app that requires 1) on non-linux and 2) on linux. Does that make any sense? Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
