From: Tejun Heo <htejun@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched/kthread: Complain loudly when others violate our flags
Date: Thu, 29 Sep 2011 20:55:01 -0700 [thread overview]
Message-ID: <20110930035501.GG10425@mtj.dyndns.org> (raw)
In-Reply-To: <1317158254.26514.55.camel@gandalf.stny.rr.com>
On Tue, Sep 27, 2011 at 05:17:34PM -0400, Steven Rostedt wrote:
> For convenience and optimization, we are going to use the task's flag
> PF_THREAD_BOUND as a way to know if a task is bound to a CPU or not. As
> that is what the flag means.
And I'm not sure this is a very good idea. Until now, PF_THREAD_BOUND
meant "this task is explicitly bound to the current affinity (whatever
it is) and thus it shouldn't be manipulated by third party". The
suggested change makes the flag much less orthogonal and useful. How
much of convenience and optimization are we talking about?
Thanks.
--
tejun
next prev parent reply other threads:[~2011-09-30 3:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 21:17 Steven Rostedt
2011-09-28 0:22 ` Thomas Gleixner
2011-09-30 3:48 ` Tejun Heo
2011-09-30 4:05 ` Steven Rostedt
2011-09-30 4:14 ` Tejun Heo
2011-09-30 8:34 ` Peter Zijlstra
2011-09-30 8:55 ` Tejun Heo
2011-09-30 9:04 ` Peter Zijlstra
2011-10-03 1:15 ` Tejun Heo
2011-10-03 10:20 ` Peter Zijlstra
2011-10-07 1:40 ` Tejun Heo
2011-10-03 10:33 ` Peter Zijlstra
2011-10-03 13:43 ` Thomas Gleixner
2011-10-03 10:50 ` Peter Zijlstra
2011-09-30 9:23 ` Peter Zijlstra
2011-09-30 9:29 ` Peter Zijlstra
2011-09-30 9:27 ` Peter Zijlstra
2011-10-03 1:22 ` Tejun Heo
2011-09-30 3:55 ` Tejun Heo [this message]
2011-09-30 4:08 ` Steven Rostedt
2011-09-30 4:28 ` Tejun Heo
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=20110930035501.GG10425@mtj.dyndns.org \
--to=htejun@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®