* New swsusp patch + Q: how to free memory?
@ 2001-09-21 21:50 Pavel Machek
0 siblings, 0 replies; only message in thread
From: Pavel Machek @ 2001-09-21 21:50 UTC (permalink / raw)
To: swsusp, ACPI mailing list, kernel list
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-09-21 21:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-09-21 21:50 New swsusp patch + Q: how to free memory? Pavel Machek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox