Re: Software Suspend Functionality in 2.5

[Nigel Cunningham <ncunningham@clear.net.nz>]

On Sat, 2003-03-01 at 04:17, Pavel Machek wrote:
> > For the kind of atomicity you need there probably are two
> > steps:
> > 1) Quiesce the system - get to a point of consistency (when you
> >    can take a resumable snapshot)
> > 2) Perform an atomic copy / snapshot
> > 
> > Step (1) would be different for swsusp and crash dump (not
> > intended to be common ). But for Step (2), do you think
> > what you need/do is complicated by crashed system requirements ?
> 
> Well, I guess count_and_copy_data_pages() is easy to share, OTOH it is
> really small piece of code. Also do you think you can free half of
> memory in crashed system? Thats what swsusp currently does...
> 
> [I need really little about LKCD... But you are going to need modified
> disk drivers etc, right? I'd like to get away without that in swsusp,
> at least in 2.6.X.]
> 

With the changes I've made, which I'm starting to merge with Pavel, I
think the two are a lot closer to each other.

With regard to quiescing the system, we need the same things stopped
that you need. We can of course use drivers_suspend when you can't, but
we could probably also use the SMP code you have.

I've got swsusp so that freeing memory is not necessary - the whole
image can be written to disk. There is still an option for the user to
aim for a smaller image (a soft limit can be set), and if there's not
enough swap available, that will also cause some memory to be freed, but
LKCD would run into that problem writing to swap too.

Regards,

Nigel