From: Tejun Heo <tj@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH REPOST v3.9-rc1] sched: replace PF_THREAD_BOUND with PF_NO_SETAFFINITY
Date: Tue, 19 Mar 2013 13:48:04 -0700 [thread overview]
Message-ID: <20130319204804.GJ3042@htj.dyndns.org> (raw)
In-Reply-To: <20130318164715.GC21516@mtj.dyndns.org>
On Mon, Mar 18, 2013 at 09:47:15AM -0700, Tejun Heo wrote:
> Hello,
>
> On Mon, Mar 18, 2013 at 10:41:40AM +0100, Ingo Molnar wrote:
> > > This patch replaces PF_THREAD_BOUND with PF_NO_SETAFFINITY.
> > > sched_setaffinity() checks the flag and return -EINVAL if set.
> > > set_cpus_allowed_ptr() is no longer affected by the flag.
> > >
> > > This will allow simplifying workqueue worker CPU affinity management.
> >
> > Acked-by: Ingo Molnar <mingo@kernel.org>
> >
> > I suspect you want to carry this in the workqueue tree, to enable those
> > extra simplifications?
>
> Yeah, I was planning to pull from one of the -tip branches but if I
> can carry it through the workqueue tree it would be simpler. Would
> that be okay?
Applying to wq/for-3.10 w/ the rebinding cleanup. Holler if this
should be routed differently.
Thanks!
--
tejun
prev parent reply other threads:[~2013-03-19 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130308204518.GR14556@mtj.dyndns.org>
2013-03-14 22:55 ` Tejun Heo
2013-03-18 9:41 ` Ingo Molnar
2013-03-18 16:47 ` Tejun Heo
2013-03-19 20:48 ` Tejun Heo [this message]
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=20130319204804.GJ3042@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®