kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: cgroup freezer
Date: Tue, 21 Feb 2012 09:23:44 +0800	[thread overview]
Message-ID: <4F42F220.8000703@gmail.com> (raw)
In-Reply-To: <CAGdaadZfn6N_sXrQuPM6JQdcni+X7k57-sVHUhPwfTBxpTcPXQ@mail.gmail.com>



On 2012?02?20? 23:06, Mulyadi Santosa wrote:
> Hi Bill :)
>
> On Mon, Feb 20, 2012 at 16:50, bill4carson<bill4carson@gmail.com>  wrote:
>> IMHO, when system load is high, administrator could freeze some of
>> cpu-hogged tasks in favor of more important ones, once system is most
>> likely to be idle, frozen tasks could be thaw back on line.
>
> what you describe, IIRC, is something doable via "batch" command
>
>> I don't know this idea is right or wrong, can somebody give me some
>> hints about practical usage of cgroup freezer?
>
> IMHO, it's also useful if you manage computer grid. So say you have 16
> nodes. A job runs on node A, but later you found that node C has the
> least load. You freeze the job and then unfreeze it in C.
>
Thanks for your reply :)
Just one silly question, how could frozen task be moved from node A to
C ?


> Of course, it assumes that the nodes are homogen. And yes, it sounds
> very similar to virtual machine migration. basically, both of them
> have same principle on how to get things done.
>
Yes, KVM+qemu have already support this feature.


-- 
I am a slow learner
but I will keep trying to fight for my dreams!

--bill

  reply	other threads:[~2012-02-21  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  9:50 cgroup freezer bill4carson
2012-02-20 15:06 ` Mulyadi Santosa
2012-02-21  1:23   ` bill4carson [this message]
2012-02-21 17:08     ` Mulyadi Santosa
2012-02-22  1:18       ` bill4carson

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=4F42F220.8000703@gmail.com \
    --to=bill4carson@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).