From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933728AbYEFWMF (ORCPT ); Tue, 6 May 2008 18:12:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758765AbYEFWLb (ORCPT ); Tue, 6 May 2008 18:11:31 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:56604 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752184AbYEFWL2 (ORCPT ); Tue, 6 May 2008 18:11:28 -0400 From: "Rafael J. Wysocki" To: pm list Subject: [RFC][PATCH 0/2] Freezer face lifting Date: Wed, 7 May 2008 00:03:55 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Ingo Molnar , Len Brown , LKML , Pavel Machek , Matt Helsley , Cedric Le Goater , Paul Menage , Andrew Morton , Alan Stern MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805070003.56387.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Although the freezer is generally considered as a bad thing, it still is being used for suspend and hibernation and will be used for these purposes in the near future. For this reason, it seems reasonable to try to reduce some known problems with it. The following two patches attempt to do that. First, it is the known weakness of the freezer that it tries to distinguish user space processes from kernel threads in a slightly artificial way. The first patch is intended to change that. Second, in principle, the freezer can use the recently introduced TASK_KILLABLE state to handle some cases that it couldn't have handled previously, which is the purpose of the second patch. Please review and tell me what you think. Rafael -- "Premature optimization is the root of all evil." - Donald Knuth