Re: Suspend 2 merge

Nigel Cunningham
2004-11-26T21:29:50Z

Hi.

On Fri, 2004-11-26 at 15:32, hugang@soulinfo.com wrote:
> > For swsusp2, you need drivers to stop the DMA, NMI not interfering,
> > sync may not happen after you have saved LRU, memory may not be
> > alocated from slab after you have saved LRU. (something else? This
> > needs to be written down somewhere, and all kernel hackers will need
> > to be carefull not to break these rules. Do you see why it wories me?)
> Ok, I got it. I think making LRU safe must sure
> 1: LRU can't change after saved.
> 2: LRU memory can't change after saved.
> The first one is done, the second we can't sure in current design, can
> we using COW do it?

2 is simple: LRU doesn't change because everything that would change it
is frozen, and the memory pool hooks ensure that scanning of the list
doesn't happen while suspending either.

I don't see the point to saving LRU pages separately when you're still
eating all the memory you can. You'll have the same number of pages to
save, just fewer to copy (and copying takes far less time than saving).

> Pagecaches still in, but disable by default, active using sysctl,
> I'd like not merge it right now, Hope other chagnes can merge into. :)

Pavel's going to think you are trying to turn swsusp into suspend2!!

Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901

You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6