Messages in this thread | | | Date | Wed, 31 Dec 2003 02:10:42 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH linux-2.6.0-test10-mm1] filemap_fdatawait.patch |
| |
Suparna Bhattacharya <suparna@in.ibm.com> wrote: > > > OK, but the thread which is running fdatawrite/fdatawait isn't interested > > in that page, because it must have been dirtied _after_ this thread has > > passed through filemap_fdatawrite(), yes? > > Not exactly. The page could actually have been dirtied _before_ this > thread passes through filemap_datawrite, but is just being parallely > written back by a background thread.
I still don't see it. If the page was dirtied before this thread entered filemap_fdatawrite() then this thread will either start writeout immediately, or will wait on the writeout and start new writeout. And the page lock avoids the timing window which you have mentioned.
- 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/
| |