| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20070220001351.GJ6133@think.oraclecorp.com> Date: Mon, 19 Feb 2007 19:13:51 -0500 From: Chris Mason <chris.mason@...cle.com> To: Miklos Szeredi <miklos@...redi.hu> Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: dirty balancing deadlock On Mon, Feb 19, 2007 at 06:11:55PM +0100, Miklos Szeredi wrote: > How about this? > > Solves the FUSE deadlock, but not the throttle_vm_writeout() one. > I'll try to tackle that one as well. > > If the per-bdi dirty counter goes below 16, balance_dirty_pages() > returns. > > Does the constant need to tunable? If it's too large, then the global > threshold is more easily exceeded. If it's too small, then in a tight > situation progress will be slower. Ok, what is supposed to happen here is that filesystems are supposed to be throttled from making more dirty pages when the system is over the threshold. Even if filesystem A doesn't have much to contribute, and filesystem B is the cause of 99% of the dirty pages, the goal of the threshold is to prevent more dirty data from happening, and filesystem A should block. But, with the producer consumer setup of fuse, I think this is a pretty good compromise. 16 dirty/writeback pages shouldn't hurt the overall limits too badly. -chris - 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