[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JHcG4-0002A9-46@pomaz-ex.szeredi.hu>
Date: Wed, 23 Jan 2008 10:51:00 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: miklos@...redi.hu
CC: a.p.zijlstra@...llo.nl, salikhmetov@...il.com, linux-mm@...ck.org,
jakob@...hought.net, linux-kernel@...r.kernel.org,
valdis.kletnieks@...edu, riel@...hat.com, ksm@...dk,
staubach@...hat.com, jesper.juhl@...il.com,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
protasnb@...il.com, miklos@...redi.hu, r.e.wolff@...wizard.nl,
hidave.darkstar@...il.com, hch@...radead.org
Subject: Re: [PATCH -v8 3/4] Enable the MS_ASYNC functionality in
sys_msync()
> > 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?
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists