[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170401020048.GF24537@linux.intel.com>
Date: Fri, 31 Mar 2017 19:00:49 -0700
From: Fenghua Yu <fenghua.yu@...el.com>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Fenghua Yu <fenghua.yu@...el.com>, Jiri Olsa <jolsa@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>, Shaohua Li <shli@...com>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/intel_rdt: Add cpus_list rdtgroup file
On Thu, Mar 30, 2017 at 04:59:47PM +0200, Jiri Olsa wrote:
> On Wed, Mar 29, 2017 at 06:16:00PM +0200, Jiri Olsa wrote:
> > On Wed, Mar 29, 2017 at 09:08:26AM -0700, Fenghua Yu wrote:
> > > On Wed, Mar 29, 2017 at 05:09:48PM +0200, Jiri Olsa wrote:
> > > > While playing with the resctrl interface I found it much
> > > > easier to deal with cpumask list rather than just regular
> > > > cpumask.
> > >
> > > Could you please explain specifically why and when it's easier
> > > to deal with cpumask list? In programming cases, cpumask
> > > and cpumask list are almost same. And people are working
> > > on higher level tools to control resctrl. The tools can
> > > hide detailed regular cpumask or cpumask list and user
> > > doesn't need to care lower level format of cpumask. So
> > > is it really useful to add cpus_list?
> >
> >
> > well I'm not aware about any such tool so I used resctrl
> > interface directly, and in that case it was much simpler
>
> is there any tool available for this actualy?
Here is a tool created by Marcelo:
https://lwn.net/Articles/710514/
Thanks.
-Fenghua
Powered by blists - more mailing lists