[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1512291338250.28591@nanos>
Date: Tue, 29 Dec 2015 13:44:16 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Marcelo Tosatti <mtosatti@...hat.com>
cc: "Yu, Fenghua" <fenghua.yu@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"x86@...nel.org" <x86@...nel.org>,
Luiz Capitulino <lcapitulino@...hat.com>,
"Shivappa, Vikas" <vikas.shivappa@...el.com>,
Tejun Heo <tj@...nel.org>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
"Luck, Tony" <tony.luck@...el.com>
Subject: Re: [RFD] CAT user space interface revisited
Marcelo,
On Wed, 23 Dec 2015, Marcelo Tosatti wrote:
> On Tue, Dec 22, 2015 at 06:12:05PM +0000, Yu, Fenghua wrote:
> > > From: Thomas Gleixner [mailto:tglx@...utronix.de]
> > >
> > > I was not able to identify any existing infrastructure where this really fits in. I
> > > chose a directory/file based representation. We certainly could do the same
> >
> > Is this be /sys/devices/system/?
> > Then create qos/cat directory. In the future, other directories may be created
> > e.g. qos/mbm?
>
> I suppose Thomas is talking about the socketmask only, as discussed in
> the call with Intel.
I have no idea about what you talked in a RH/Intel call.
> Thomas, is that correct? (if you want a change in directory structure,
> please explain the whys, because we don't need that change in directory
> structure).
Can you please start to write coherent and understandable mails? I have no
idea of which directory structure, which does not need to be changed, you are
talking.
I described a directory structure for that qos/cat stuff in my proposal and
that's complete AFAICT.
Thanks,
tglx
--
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