Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934456AbbEMNyo (ORCPT ); Wed, 13 May 2015 09:54:44 -0400 Received: from mail-qg0-f43.google.com ([209.85.192.43]:33716 "EHLO mail-qg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754295AbbEMNym (ORCPT ); Wed, 13 May 2015 09:54:42 -0400 Date: Wed, 13 May 2015 09:54:38 -0400 From: Tejun Heo To: Kyungmin Park Cc: linux-mm , Andrew Morton , "\\Rafael J. Wysocki\\" , David Rientjes , Johannes Weiner , Oleg Nesterov , Cong Wang , LKML , Linux PM list Subject: Re: [RFC PATCH] PM, freezer: Don't thaw when it's intended frozen processes Message-ID: <20150513135438.GR11388@htj.duckdns.org> References: <20150507064557.GA26928@july> <20150507154212.GA12245@htj.duckdns.org> <20150508152513.GB28439@htj.duckdns.org> <20150512144313.GO11388@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 20 On Wed, May 13, 2015 at 09:42:47AM +0900, Kyungmin Park wrote: > Right, it's still in freezer, just one time scheduling is happened. > and enter freeze state again. > > do you think can we avoid it or it's sub-optimal to do as patch? I mean, it's suboptimal. I'm not sure it actually matters tho. If it matters, please feel free to submit a patch with proper rationale. Please just be careful so that we don't miss sending out wakeup in case we race against thawing. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/