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 10:03:33 +0100 [thread overview]
Message-ID: <20151116090333.GL17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20151113140438.3d8e2e11@redhat.com>
On Fri, Nov 13, 2015 at 02:04:38PM -0500, Luiz Capitulino wrote:
> I guess that what Peter is saying is that we don't want tasks
> attached to a reservation landing on a CPU where the reservation
> might be different or not existent at all.
Correct.
> This way, the ATTACH_RESERVATION command would fail if any
> of the CPUs in the cpumask are not part of the reservation.
> And then our code would have to be notified any time the process'
> affinity mask is changed (we either fail the affinity change
> or detach the process automatically from the reservation). Does
> this sound like a good solution?
No. We're not going to have random drivers muck about with affinity
masks, and most certainly not some manky ioctl.
next prev parent reply other threads:[~2015-11-16 9:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 16:39 [PATCH RFC] ioctl based CAT interface 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 [this message]
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
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=20151116090333.GL17308@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.