From: Miklos Szeredi <miklos@szeredi.hu>
To: Maxim Patlasov <MPatlasov@parallels.com>
Cc: Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
riel@redhat.com, Kirill Korotaev <dev@parallels.com>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Brian Foster <bfoster@redhat.com>,
Pavel Emelianov <xemul@parallels.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Bottomley <jbottomley@parallels.com>,
linux-mm@kvack.org, Al Viro <viro@zeniv.linux.org.uk>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
fengguang.wu@intel.com, devel@openvz.org,
Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH] mm: strictlimit feature -v3
Date: Mon, 15 Jul 2013 12:35:23 +0200 [thread overview]
Message-ID: <CAJfpegtNRxacv3Lw0XOK7zuQJB0_NttNzw7p3fQE+J7T_dZHyQ@mail.gmail.com> (raw)
In-Reply-To: <CAPB2xN89n=1JLQe7w_+J8A246HsUDv0oP1WCjQ=4OFJnDDGchQ@mail.gmail.com>
On Thu, Jul 11, 2013 at 11:50 PM, Maxim Patlasov
<MPatlasov@parallels.com> wrote:
> On Thu, Jul 11, 2013 at 10:51 PM, Jan Kara <jack@suse.cz> 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-07-15 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 15:53 Maxim Patlasov
2013-07-11 18:51 ` Jan Kara
2013-07-11 21:50 ` Maxim Patlasov
2013-07-15 10:35 ` Miklos Szeredi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJfpegtNRxacv3Lw0XOK7zuQJB0_NttNzw7p3fQE+J7T_dZHyQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=MPatlasov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=dev@parallels.com \
--cc=devel@openvz.org \
--cc=fengguang.wu@intel.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jack@suse.cz \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox