From: Pavel Machek <pavel@suse.cz>
To: swsusp@lister.fornax.hu,
ACPI mailing list <acpi@phobos.fachschaften.tu-muenchen.de>,
kernel list <linux-kernel@vger.kernel.org>
Subject: New swsusp patch + Q: how to free memory?
Date: Fri, 21 Sep 2001 23:50:25 +0200 [thread overview]
Message-ID: <20010921235025.A308@bug.ucw.cz> (raw)
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
reply other threads:[~2001-09-21 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010921235025.A308@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi@phobos.fachschaften.tu-muenchen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=swsusp@lister.fornax.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox