Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Lennart Poettering
On Wed, 20.07.16 14:49, Daniel P. Berrange (berra...@redhat.com) wrote: > > > The key factor here is use of "Before" to ensure this gets run immediately > > > after systemd switches root out of the initrd, and before /any/ long lived > > > services are run. This lets us set cpuset placement on

Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Daniel P. Berrange
On Wed, Jul 20, 2016 at 03:29:30PM +0200, Lennart Poettering wrote: > On Wed, 20.07.16 12:53, Daniel P. Berrange (berra...@redhat.com) wrote: > > > For virtualized hosts it is quite common to want to confine all host OS > > processes to a subset of CPUs/RAM nodes, leaving the rest available for >

Re: [systemd-devel] Confining ALL processes to a CPUs/RAM via cpuset controller

2016-07-20 Thread Lennart Poettering
On Wed, 20.07.16 12:53, Daniel P. Berrange (berra...@redhat.com) wrote: > For virtualized hosts it is quite common to want to confine all host OS > processes to a subset of CPUs/RAM nodes, leaving the rest available for > exclusive use by QEMU/KVM. Historically people have used the "isolcpus" >