From mboxrd@z Thu Jan 1 00:00:00 1970 In-reply-to: <1191581854.22357.85.camel@twins> (message from Peter Zijlstra on Fri, 05 Oct 2007 12:57:34 +0200) Subject: Re: [PATCH] remove throttle_vm_writeout() References: <20071004145640.18ced770.akpm@linux-foundation.org> <20071004160941.e0c0c7e5.akpm@linux-foundation.org> <20071004164801.d8478727.akpm@linux-foundation.org> <20071004174851.b34a3220.akpm@linux-foundation.org> <1191572520.22357.42.camel@twins> <1191577623.22357.69.camel@twins> <1191581854.22357.85.camel@twins> Message-Id: From: Miklos Szeredi Date: Fri, 05 Oct 2007 13:27:16 +0200 Sender: owner-linux-mm@kvack.org Return-Path: To: a.p.zijlstra@chello.nl Cc: miklos@szeredi.hu, akpm@linux-foundation.org, wfg@mail.ustc.edu.cn, linux-mm@kvack.org, linux-kernel@vger.kernel.org, trond.myklebust@fys.uio.no List-ID: > Limiting FUSE to say 50% (suggestion from your other email) sounds like > a horrible hack to me. - Need more time to think on this. I don't really understand all that page balancing stuff, but I think this will probably never or very rarely happen, because the allocator will prefer the bigger zones, and the dirty page limiting will not let the bigger zones get too full of dirty pages. And even it can happen, it's not necessarily a fuse-only thing. It makes tons of sense to make sure, that we don't fully dirty _any_ specialized zone. One special zone group are the low-memory pages. And currently balance_dirty_pages() makes sure we don't fill that up with dirty file backed pages. So something like that should make sense for other special zones like DMA as well. I'm not saying it's trivial, or even possible to implement, just thinking... Miklos -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org