[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJfpegvmrFywtwS5giuCgVc5Cr3G1+fXKTPYiCZsV5P1jinxXA@mail.gmail.com>
Date: Wed, 20 Feb 2013 14:13:54 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: "Li, Fei" <fei.li@...el.com>
Cc: Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
"Brown, Len" <len.brown@...el.com>,
"Wang, Biao" <biao.wang@...el.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"fuse-devel@...ts.sourceforge.net" <fuse-devel@...ts.sourceforge.net>,
"mingo@...hat.com" <mingo@...hat.com>,
"Liu, Chuansheng" <chuansheng.liu@...el.com>
Subject: Re: [fuse-devel] Getting rid of freezer for suspend [was Re: [PATCH]
fuse: make fuse daemon frozen along with kernel threads]
On Wed, Feb 20, 2013 at 3:54 AM, Li, Fei <fei.li@...el.com> wrote:
>> From: Pavel Machek [mailto:pavel@....cz]
>>
>> freeze_priority?
>>
>> I _hope_ we will not need more than three priorities, (user, fused, kernel), but
>> I hoped not no need more than two before, so...
>
> IMHO, we still use two priorities, with the exception that user space process such
> as fuse daemon can be configured to be frozen in kernel threads frozen phase
> instead of user space processes frozen phase.
I'm not sure that will work. Fuse processes are in fact ordinary
userspace processes, and so should be frozen before kernel threads.
Thanks,
Miklos
--
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