Re: [PATCH] Thaw userspace and kernel space separately.

["Rafael J. Wysocki" <rjw@sisk.pl>]

On Monday, 23 October 2006 14:00, Nigel Cunningham wrote:
> Hi.
> 
> On Mon, 2006-10-23 at 12:26 +0200, Rafael J. Wysocki wrote:
> > On Monday, 23 October 2006 01:48, Nigel Cunningham wrote:
> > > Modify process thawing so that we can thaw kernel space without thawing
> > > userspace, and thaw kernelspace first. This will be useful in later
> > > patches, where I intend to get swsusp thawing kernel threads only before
> > > seeking to free memory.
> > 
> > Please explain why you think it will be necessary/useful.
> > 
> > I remember a discussion about it some time ago that didn't indicate
> > we would need/want to do this.
> 
> This is needed to make suspending faster and more reliable when the
> system is in a low memory situation. Imagine that you have a number of
> processes trying to allocate memory at the time you're trying to
> suspend. They want so much memory that when you come to prepare the
> image, you find that you need to free pages. But your swapfile is on
> ext3, and you've just frozen all processes, so any attempt to free
> memory could result in a deadlock while the vm tries to swap out pages
> using the frozen kjournald.

This is not true, sorry.

Swapfiles are handled at the block device level.  The filesystem is only
needed when you run swapon, to create swap extents that are used later
to handle the swap file.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller