From: Mingliang <longapple@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Is there a way to force suspended process's memory to swap space?
Date: Tue, 14 Apr 2009 00:03:35 -0800 [thread overview]
Message-ID: <56b13acf0904140103x52978583hdf00ba46d5fa3c73@mail.gmail.com> (raw)
Hi,
For example, my process continuously consumes 30MB memory.
$ ps aux|grep job
joe 17941 0.0 0.3 33104 31096 pts/16 S 15:50 0:00 ./job 30
^^^^^^^
Now I stop it
$kill -STOP 17941
[1]+ Stopped ./job 30
$ ps aux|grep job
joe 17941 0.0 0.3 33104 31096 pts/16 T 15:50 0:00 ./job 30
So it doesn't consume CPU time any more, BUT is there also a way to
swap out the 30MB memory?
Can it be accomplished manually (some signal, maybe?) or is it only
the kernel who can make decision?
Any of your suggestion is much appreciated.
Regards,
Joe
next reply other threads:[~2009-04-14 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 8:03 Mingliang [this message]
2009-04-15 3:28 ` Is there a way to force suspended process's memory to swap space? Glynn Clements
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=56b13acf0904140103x52978583hdf00ba46d5fa3c73@mail.gmail.com \
--to=longapple@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).