From mboxrd@z Thu Jan 1 00:00:00 1970 From: bill4carson@gmail.com (bill4carson) Date: Tue, 21 Feb 2012 09:23:44 +0800 Subject: cgroup freezer In-Reply-To: References: <4F42176C.9070709@gmail.com> Message-ID: <4F42F220.8000703@gmail.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On 2012?02?20? 23:06, Mulyadi Santosa wrote: > Hi Bill :) > > On Mon, Feb 20, 2012 at 16:50, bill4carson 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