From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752251AbbKPJIg (ORCPT <rfc822;w@1wt.eu>);
	Mon, 16 Nov 2015 04:08:36 -0500
Received: from bombadil.infradead.org ([198.137.202.9]:57168 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750932AbbKPJIc (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 16 Nov 2015 04:08:32 -0500
Date: Mon, 16 Nov 2015 10:07:56 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Vikas Shivappa <vikas.shivappa@intel.com>, Tejun Heo <tj@kernel.org>,
        Yu Fenghua <fenghua.yu@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] ioctl based CAT interface
Message-ID: <20151116090756.GM17308@twins.programming.kicks-ass.net>
References: <20151113163933.GA10222@amt.cnet>
 <20151113165100.GI17308@twins.programming.kicks-ass.net>
 <20151113173303.GB13490@amt.cnet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20151113173303.GB13490@amt.cnet>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Nov 13, 2015 at 03:33:04PM -0200, Marcelo Tosatti wrote:
> On Fri, Nov 13, 2015 at 05:51:00PM +0100, Peter Zijlstra wrote:
> > On Fri, Nov 13, 2015 at 02:39:33PM -0200, Marcelo Tosatti wrote:
> > > + * 	* one tcrid entry can be in different locations 
> > > + * 	  in different sockets.
> > 
> > NAK on that without cpuset integration.
> > 
> > I do not want freely migratable tasks having radically different
> > performance profiles depending on which CPU they land.
> 
> Ok, so, configuration:
> 
> 
> Socket-1				Socket-2
> 
> pinned thread-A with			100% L3 free
> 80% of L3 
> reserved
> 
> 
> So it is a problem if a thread running on socket-2 is scheduled to 
> socket-1 because performance is radically different, fine.
> 
> Then one way to avoid that is to not allow freely migratable tasks
> to move to Socket-1. Fine.
> 
> Then you want to use cpusets for that.
> 
> Can you fill in the blanks what is missing here?

I'm still not seeing what the problem with CAT-cgroup is.

/cgroups/cpuset/
  socket-1/cpus = $socket-1
           tasks = $thread-A

  socket-2/cpus = $socket-2
           tasks = $thread-B

/cgroups/cat/
  group-A/bitmap = 0x3F / 0xFF
  group-A/tasks = $thread-A

  group-B/bitmap = 0xFF / 0xFF
  group-B/tasks = $thread-B


That gets you thread-A on socket-1 with 6/8 of the L3 and thread-B on
socket-2 with 8/8 of the L3.