[lkml]   [2001]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectNew swsusp patch + Q: how to free memory?

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

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.

I'm "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.020 / U:1.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site