From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx149.postini.com [74.125.245.149]) by kanga.kvack.org (Postfix) with SMTP id 7B88D6B00C9 for ; Mon, 15 Jul 2013 06:35:24 -0400 (EDT) Received: by mail-qc0-f170.google.com with SMTP id s1so6169724qcw.29 for ; Mon, 15 Jul 2013 03:35:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20130705155113.3586.78292.stgit@maximpc.sw.ru> <20130711185104.GC5349@quack.suse.cz> Date: Mon, 15 Jul 2013 12:35:23 +0200 Message-ID: Subject: Re: [PATCH] mm: strictlimit feature -v3 From: Miklos Szeredi Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Maxim Patlasov Cc: Jan Kara , Andrew Morton , riel@redhat.com, Kirill Korotaev , fuse-devel , Brian Foster , Pavel Emelianov , Kernel Mailing List , James Bottomley , linux-mm@kvack.org, Al Viro , Linux-Fsdevel , fengguang.wu@intel.com, devel@openvz.org, Mel Gorman On Thu, Jul 11, 2013 at 11:50 PM, Maxim Patlasov wrote: > On Thu, Jul 11, 2013 at 10:51 PM, Jan Kara wrote: [snipped] >> If I'm right in the above, then removing NR_WRITEBACK_TEMP would be a nice >> followup patch. > > I'd rather introduce the notion of trusted fuse filesystem. If system > administrator believe given fuse fs "trusted", it works w/o > strictlimit, but fuse daemon is supposed to notify the kernel > explicitly about threads related to processing writeback. The kernel > would raise a per-task flag for those threads. And, calculating > nr_dirty in balance_dirty_pages, we'd add NR_WRITEBACK_TEMP for all, > excepting tasks with the flag set. This is very simple and will work > perfectly. Yes, doing a trusted mode for fuse is a good idea, I think. And it should have a new filesystem type (can't think of a good name though, "fusetrusted" is a bit too long). Thanks, 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