On Thu, 25 Feb 2016 17:53:30 -0500
John Ferlan wrote:
> On 02/23/2016 10:58 AM, Henning Schild wrote:
> > Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
> > we move the one main thread right into the emulator cgroup, instead
> > of moving multiple threads
On Thu, 25 Feb 2016 17:53:30 -0500
John Ferlan wrote:
> On 02/23/2016 10:58 AM, Henning Schild wrote:
> > Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
> > we move the one main thread right into the emulator cgroup, instead
> > of moving multiple threads
On Fri, 26 Feb 2016 11:14:31 +
"Daniel P. Berrange" wrote:
> On Tue, Feb 23, 2016 at 04:58:40PM +0100, Henning Schild wrote:
> > Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
> > we move the one main thread right into the emulator cgroup, instead
> >
On Tue, Feb 23, 2016 at 04:58:40PM +0100, Henning Schild wrote:
> Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
> we move the one main thread right into the emulator cgroup, instead
> of moving multiple threads later on. And we do not actually want any
> threads running in the
On 02/23/2016 10:58 AM, Henning Schild wrote:
> Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
> we move the one main thread right into the emulator cgroup, instead
> of moving multiple threads later on. And we do not actually want any
> threads running in the parent cgroups
Move qemuSetupCgroupForEmulator up under qemuSetupCgroup. That way
we move the one main thread right into the emulator cgroup, instead
of moving multiple threads later on. And we do not actually want any
threads running in the parent cgroups (cpu cpuacct cpuset).
Signed-off-by: Henning Schild