From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753816Ab1I1IAi (ORCPT ); Wed, 28 Sep 2011 04:00:38 -0400 Received: from beauty.rexursive.com ([150.101.121.179]:53380 "EHLO beauty.rexursive.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751343Ab1I1IAh (ORCPT ); Wed, 28 Sep 2011 04:00:37 -0400 Subject: Re: [PATCH v5]: Improve performance of LZO hibernation From: Bojan Smojver To: Pekka Enberg Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" Date: Wed, 28 Sep 2011 18:00:36 +1000 In-Reply-To: References: <1317183650.2067.10.camel@shrek.rexursive.com> <1317194947.1998.18.camel@shrek.rexursive.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.0.3 (3.0.3-1.fc15) Content-Transfer-Encoding: 7bit Message-ID: <1317196836.1998.29.camel@shrek.rexursive.com> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2011-09-28 at 10:48 +0300, Pekka Enberg wrote: > Yes, the threads are stopped. What happens after that? Will the > hibernation process be aborted? How can this be tested? Oh, I didn't answer the other possibility - that we stopped the threads form hibernation code. This is what we want. Compression/decompression threads stop on our request (i.e. not an error). We continue with the process, because there is no more data to compress/decompress. -- Bojan