New swsusp patch + Q: how to free memory?

From: Pavel Machek (pavel@suse.cz)
Date: Fri Sep 21 2001 - 16:50:25 EST

Next message: Pavel Machek: "new swsusp patch [this time for real]"
Previous message: DICKENS,CARY (HP-Loveland,ex2): "RE: major VM with 2.4.10pre12 and 2.4.10pre13 and highmem, we w ill help test"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi!

Here's new swsusp patch. It no longer adds signals (breaking ABI), and
it now should work okay with journaling filesystems. Hardware state
restore is (mostly) not done -- that's task for someone else, like
ACPI.

Last big remaining problem is "how to free memory". What's currently
in swsusp patch just does no work. Any advice wanted. Don't try with
hard real-time tasks. (Funny question: should suspend be supported
with such beasts around? ;-). Oh and we have some by-design problems
with network. Maybe some packets will be sent twice.

I wanted to free memory by eat_memory() followed by free_memory(), but
that's big no-no from context swsusp is using.
Pavel

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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/

Next message: Pavel Machek: "new swsusp patch [this time for real]"
Previous message: DICKENS,CARY (HP-Loveland,ex2): "RE: major VM with 2.4.10pre12 and 2.4.10pre13 and highmem, we w ill help test"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Sep 23 2001 - 21:00:45 EST