Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751695AbWEKNUq (ORCPT ); Thu, 11 May 2006 09:20:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751698AbWEKNUq (ORCPT ); Thu, 11 May 2006 09:20:46 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:21701 "EHLO ogre.sisk.pl") by vger.kernel.org with ESMTP id S1751669AbWEKNUp convert rfc822-to-8bit (ORCPT ); Thu, 11 May 2006 09:20:45 -0400 From: "Rafael J. Wysocki" To: Nigel Cunningham Subject: Re: [PATCH -mm] swsusp: support creating bigger images (rev. 2) Date: Thu, 11 May 2006 15:20:29 +0200 User-Agent: KMail/1.9.1 Cc: Andrew Morton , linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au, pavel@suse.cz References: <200605021200.37424.rjw@sisk.pl> <20060510163833.586b93ce.akpm@osdl.org> <200605111011.23508.ncunningham@cyclades.com> In-Reply-To: <200605111011.23508.ncunningham@cyclades.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Content-Disposition: inline Message-Id: <200605111520.30203.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3335 Lines: 69 Hi, On Thursday 11 May 2006 02:11, Nigel Cunningham wrote: > Hi Andrew et al. > > On Thursday 11 May 2006 09:38, Andrew Morton wrote: > > "Rafael J. Wysocki" wrote: > > > On Wednesday 10 May 2006 00:27, Andrew Morton wrote: > > > > "Rafael J. Wysocki" wrote: > > > > > Now if the mapped pages that are not mapped by the > > > > > current task are considered, it turns out that they would change > > > > > only if they were reclaimed by try_to_free_pages().  Thus if we take > > > > > them out of reach of try_to_free_pages(), for example by > > > > > (temporarily) moving them out of their respective LRU lists after > > > > > creating the image, we will be able to include them in the image > > > > > without copying. > > > > > > > > I'm a bit curious about how this is true. There are all sorts of way > > > > in which there could be activity against these pages - interrupt-time > > > > asynchronous network Tx completion, async interrupt-time direct-io > > > > completion, tasklets, schedule_work(), etc, etc. > > > > > > AFAIK, many of these things are waited for uninterruptibly, and > > > uninterruptible tasks cannot be frozen. > > > > There can be situations where we won't be waiting on this IO at all. > > Network zero-copy transmit, for example. > > > > Or maybe there's some async writeback going on against pagecache - we'll > > end up looking at the page's LRU state within interrupt context at IO > > completion. (A sync would prevent this from happening). > > I believe more than a sync is needed in at least some cases. I've seen XFS > continue to submit I/O (presumably on the sb or such like) after everything > else has been frozen and data has been synced. Freezing bdevs addressed this. > > > One possibly problematic scenario is where task A is doing a direct-IO read > > and task B truncates the same file - here, the page will be actually > > removed from the LRU and freed in interrupt context. The direct-IO read > > process will be waiting on the IO in D state though. It it was a > > synchronous read - if it was an AIO read then it won't be waiting on the > > IO. Something else might save us here, but it's fragile. > > Bdev freezing helps here too, right? Well, I'm not sure. How exactly? > > > Theoretically we may have a problem if there's an > > > interruptible task that waits for the completion of an operation that > > > gets finished after snapshotting the system. However that would have to > > > survive the syncing of filesystems, freezing of kernel threads, freeing > > > of memory as well as suspending and resuming all devices. [In which case > > > it would be starving to death. :-)] > > (For Rafael/Pavel): The swsusp version of the refrigerator signals these > processes to enter the freezer too, just in case the uninterruptible task > does continue, right? Uninterruptible tasks are not freezable with the swsusp's freezer at all. The other tasks are signaled to enter the refrigerator - first user space, then we sync filesystems and finally we freeze kernel threads. Greetings, Rafael - 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/