[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151016095022.GP3816@twins.programming.kicks-ass.net>
Date: Fri, 16 Oct 2015 11:50:22 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Marcelo Tosatti <mtosatti@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Fenghua Yu <fenghua.yu@...el.com>,
H Peter Anvin <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
x86 <x86@...nel.org>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>
Subject: Re: [PATCH V15 00/11] x86: Intel Cache Allocation Technology Support
On Thu, Oct 15, 2015 at 11:28:52PM -0300, Marcelo Tosatti wrote:
> On Thu, Oct 15, 2015 at 01:36:14PM +0200, Peter Zijlstra wrote:
> > On Tue, Oct 13, 2015 at 06:31:27PM -0300, Marcelo Tosatti wrote:
> > > I am rewriting the interface with ioctls, with commands similar to the
> > > syscall interface proposed.
> >
> > Which is horrible for other use cases. I really don't see the problem
> > with the cgroup stuff.
>
> Can you detail what "horrible" means?
Say an RT scenario; you set up your machine with cgroups. You create a
cpuset with is disjoint from the others, you frob around with the cpu
cgroup, etc..
So once you're all done, you start your RT app into a cgroup.
But oh, fail, now you have to go muck about with ioctl()s to get the
cache allocation cruft to work.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists