[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JHmxa-0004BK-6X@pomaz-ex.szeredi.hu>
Date: Wed, 23 Jan 2008 22:16:38 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: torvalds@...ux-foundation.org
CC: miklos@...redi.hu, 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, akpm@...ux-foundation.org,
protasnb@...il.com, 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()
> So it's not horribly hard, but it's kind of a separate issue right now.
> And while the *generic* page-writeback is easy enough to fix, I worry
> about low-level filesystems that have their own "writepages()"
> implementation. They could easily get that wrong.
Yeah, nasty.
How about doing it in a separate pass, similarly to
wait_on_page_writeback()? Just instead of waiting, clean the page
tables for writeback pages.
> So right now it seems that waiting for writeback to finish is the right
> and safe thing to do (and even so, I'm not actually willing to commit my
> suggested patch in 2.6.24, I think this needs more thinking about)
Sure, I would have though all of this stuff is 2.6.25, but it's your
kernel... :)
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