mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Marcelo Tosatti <mtosatti@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
Date: Mon, 16 Nov 2015 17:26:57 +0100	[thread overview]
Message-ID: <20151116162657.GX17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20151116111842.0c0a30f9@redhat.com>

On Mon, Nov 16, 2015 at 11:18:42AM -0500, Luiz Capitulino wrote:
> Peter, I'm giving a serious try on the cgroups patches and would be
> glad to be enlightened if I'm missing something. But I don't see how
> what you're proposing would solve the problem.
> 
> My understanding of CAT is that if I want to reserve 80% of the cache
> in socket-1 to $thread-A I also have to:
> 
>  1. Create another mask reserving 20% of the cache in socket-1
>  2. Assign that mask to all other threads that may run in socket-1
> 
> If I'm right about this, then when a task with 20% reservation migrates
> to socket-2 it will only access 20% of the cache there even though there
> should be no restrictions in socket-2's cache.

Uh what? Task-A was bound to socket-1, it will never get to socket-2.

Clearly I'm not getting these examples you're throwing around.

Also, I explicitly do not want tasks that can migrate between sockets to
have different performance profiles across those sockets.

  reply	other threads:[~2015-11-16 16:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 16:39 Marcelo Tosatti
2015-11-13 16:51 ` Peter Zijlstra
2015-11-13 17:27   ` Marcelo Tosatti
2015-11-13 17:43     ` Marcelo Tosatti
2015-11-16  8:59       ` Peter Zijlstra
2015-11-16 13:03         ` Marcelo Tosatti
2015-11-16 14:42           ` Thomas Gleixner
2015-11-16 19:52             ` Marcelo Tosatti
2015-11-16 15:01           ` Peter Zijlstra
2015-11-16 19:54             ` Marcelo Tosatti
2015-11-16 21:22             ` Marcelo Tosatti
2015-11-13 19:04     ` Luiz Capitulino
2015-11-13 20:22       ` Marcelo Tosatti
2015-11-16  9:03       ` Peter Zijlstra
2015-11-13 17:33   ` Marcelo Tosatti
2015-11-16  9:07     ` Peter Zijlstra
2015-11-16 14:37       ` Marcelo Tosatti
2015-11-16 15:37         ` Peter Zijlstra
2015-11-16 16:18       ` Luiz Capitulino
2015-11-16 16:26         ` Peter Zijlstra [this message]
2015-11-16 16:48           ` Luiz Capitulino
2015-11-16 16:39       ` Marcelo Tosatti
2015-11-17  1:01         ` Marcelo Tosatti
2015-11-13 18:01   ` Marcelo Tosatti
2015-11-16  9:09     ` Peter Zijlstra
2015-11-13 19:08 ` Luiz Capitulino
2015-12-03 21:58 ` Pavel Machek

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=20151116162657.GX17308@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=vikas.shivappa@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

Powered by JetHome