public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vikas Shivappa <vikas.shivappa@intel.com>
Cc: Matt Fleming <matt@console-pimps.org>,
	vikas <vikas.shivappa@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	"matt.fleming" <matt.fleming@intel.com>,
	"will.auld" <will.auld@intel.com>,
	tj@kernel.org
Subject: Re: Cache Allocation Technology Design
Date: Wed, 29 Oct 2014 19:16:54 +0100	[thread overview]
Message-ID: <20141029181654.GR12706@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1410291020020.26215@vshiva-Udesk>

On Wed, Oct 29, 2014 at 10:26:16AM -0700, Vikas Shivappa wrote:
> >It appears to me this 'mode' thing is entirely superfluous and can be
> >constructed by voluntary operation of this and cpusets or manual
> >affinity calls.
> 
> Do you mean user would would just user the cpusets for cpu affinity and CAT
> cgroup for cache allocation as shown in example below ?
> 
> In other words say affinitize the PID1 and PID2 to CPUs 1 and 2
>  and then set the desired cache allocation as well like below - then we have
> the desired cpu affinity and cache allocation for these PIDs..
> 
> cd /sys/fs/cgroup/cpuset
> 
> mkdir group1_specialuse
> /bin/echo 1-2 > cpuset.cpus
> /bin/echo PID1 > tasks
> /bin/echo PID2 > tasks
> 
> Now come to CAT and do the cache allocation for the same tasks PID1 and
> PID2.
> 
> cd /sys/fs/cgroup/cat (CAT cgroup)
> 
> mkdir group1_specialuse (keeping same name just for understanding)
> /bin/echo 0xf > cat.cbm (set the cache bit mask)
> /bin/echo PID1 > tasks
> /bin/echo PID2 > tasks
> 

Yah, except I have a strong urge to mount cpusets under /dog when you
put it like that ;-)

Or co-mount cpusets and pets and do it that way.

  reply	other threads:[~2014-10-29 18:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 18:44 Cache Allocation Technology Design vikas
2014-10-20 16:18 ` Matt Fleming
2014-10-24 10:53   ` Peter Zijlstra
2014-10-28 23:22     ` Matt Fleming
2014-10-29  8:16       ` Peter Zijlstra
2014-10-29 12:48         ` Matt Fleming
2014-10-29 13:45           ` Peter Zijlstra
2014-10-29 16:32             ` Auld, Will
2014-10-29 17:28               ` Peter Zijlstra
2014-10-29 17:41                 ` Vikas Shivappa
2014-10-29 18:22                   ` Tejun Heo
2014-10-30  7:07                     ` Peter Zijlstra
2014-10-30  7:14                       ` Peter Zijlstra
2014-10-30 12:44                         ` Tejun Heo
2014-10-30 13:19                           ` Peter Zijlstra
2014-10-30 15:25                             ` Tejun Heo
2014-10-30 12:43                       ` Tejun Heo
2014-10-30 13:18                         ` Peter Zijlstra
2014-10-30 17:03                           ` Tejun Heo
2014-10-30 21:43                             ` Peter Zijlstra
2014-10-30 22:22                               ` Tejun Heo
2014-10-30 22:47                                 ` Peter Zijlstra
2014-11-06 16:27                                   ` Matt Fleming
2014-11-06 17:20                                     ` Vikas Shivappa
2014-10-31 13:07                                 ` Peter Zijlstra
2014-10-31 15:58                                   ` Tejun Heo
2014-11-04 13:13                                     ` Peter Zijlstra
2014-11-05 20:41                                       ` Tejun Heo
2014-10-30 14:14                         ` Matt Fleming
     [not found]                         ` <CAAAKZwvJOKsrj_yczDGaNLaNYo+_=HzsTLwDdcaTJqO2VMy8uA@mail.gmail.com>
2014-10-30 17:12                           ` Tejun Heo
2014-10-30 22:35                             ` Tim Hockin
2014-10-31 16:57                               ` Tejun Heo
2014-10-30 23:18                         ` Vikas Shivappa
2014-11-04 13:17                           ` Peter Zijlstra
2014-11-06 17:03                             ` Matt Fleming
2014-11-10 15:50                               ` Peter Zijlstra
2014-10-29 17:26     ` Vikas Shivappa
2014-10-29 18:16       ` Peter Zijlstra [this message]
2014-11-03 23:29 ` Vikas Shivappa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141029181654.GR12706@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt@console-pimps.org \
    --cc=tj@kernel.org \
    --cc=vikas.shivappa@intel.com \
    --cc=vikas.shivappa@linux.intel.com \
    --cc=will.auld@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox