Re: [PATCH -v8 3/4] Enable the MS_ASYNC functionality in sys_msync()

From: Anton Salikhmetov
Date: Wed Jan 23 2008 - 08:09:29 EST


2008/1/23, Miklos Szeredi <miklos@xxxxxxxxxx>:
> > > Also, it still doesn't make sense to me why we'd not need to walk the
> > > rmap, it is all the same file after all.
> >
> > It's the same file, but not the same memory map. It basically depends
> > on how you define msync:
> >
> > a) sync _file_ on region defined by this mmap/start/end-address
> > b) sync _memory_region_ defined by start/end-address
>
> My mmap/msync tester program can acually check this as well, with the
> '-f' flag. Anton, can you try that on the reference platforms?

Here it is:

$ ./a.out file -f
begin 1201085546 1201085546 1200956936
write 1201085546 1201085546 1200956936
mmap 1201085546 1201085546 1200956936
b 1201085546 1201085546 1200956936
msync b 1201085550 1201085550 1200956936
c 1201085550 1201085550 1200956936
msync c 1201085552 1201085552 1200956936
d 1201085552 1201085552 1200956936
munmap 1201085552 1201085552 1200956936
close 1201085555 1201085555 1200956936
sync 1201085555 1201085555 1200956936
$ ./a.out file -sf
begin 1201085572 1201085572 1200956936
write 1201085572 1201085572 1200956936
mmap 1201085572 1201085572 1200956936
b 1201085572 1201085572 1200956936
msync b 1201085576 1201085576 1200956936
c 1201085576 1201085576 1200956936
msync c 1201085578 1201085578 1200956936
d 1201085578 1201085578 1200956936
munmap 1201085578 1201085578 1200956936
close 1201085581 1201085581 1200956936
sync 1201085581 1201085581 1200956936
$ uname -a
FreeBSD td152.testdrive.hp.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri
Jan 12 11:05:30 UTC 2007
root@xxxxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/SMP i386
$

>
> Miklos
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/