I have more up to date versions of these patches around here. The problem with them is that fundamentally, the WAPBL implementation as it is assumes that it may infinitely steal buffers from the buffer cache and hold onto them indefinitely - and it assumes it can always get buffers from it. While the patch as it sits may "work" in the "happy case" on many people's machines, as it sits today it is dangerous and can lock up your machine and corrupt things in low memory situations.
Basically in order to progres WAPBL (renamed "FFS Journalling" here) needs to have a mechanism added to allow it be told "no it can't have a buffer" and let it deal with it correctly. The first part is done, the latter part is complex. On Sat, Mar 26, 2016 at 1:27 PM, Martijn Rijkeboer <mart...@bunix.org> wrote: > Hi, > > Just out of curiosity, what has happend with WAPBL? There were some patches > floating around on tech@ in the last months of 2015, but then it became > quiet. I'm not complaining just curious. > > Kind regards, > > > Martijn Rijkeboer
