From: Peter Zijlstra <peterz@infradead.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: john stultz <johnstul@us.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: rcu stalls seen with numasched_v2 patches applied.
Date: Wed, 08 Aug 2012 21:58:58 +0200 [thread overview]
Message-ID: <1344455938.16728.13.camel@laptop> (raw)
In-Reply-To: <20120807171859.GB3850@linux.vnet.ibm.com>
On Tue, 2012-08-07 at 22:49 +0530, Srikar Dronamraju wrote:
> Are you referring to this the commit 158e1645e (trim task_work: get rid of hlist)
No, to something like the below..
> I am also able to reproduce this on another 8 node machine too.
Ship me one ;-)
> Just to update, I had to revert commit: b9403130a5 sched/cleanups: Add
> load balance cpumask pointer to 'struct lb_env' so that your patches
> apply cleanly. (I dont think this should have caused any problem.. but)
Yeah, I've got a rebase on top of that.. just wanted fold this
page::last_nid thing into the page::flags before posting again.
---
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1539,6 +1539,7 @@ struct task_struct {
#ifdef CONFIG_SMP
u64 node_stamp; /* migration stamp */
unsigned long numa_contrib;
+ struct callback_head numa_work;
#endif /* CONFIG_SMP */
#endif /* CONFIG_NUMA */
struct rcu_head rcu;
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -816,7 +816,7 @@ void task_numa_work(struct callback_head
struct task_struct *t, *p = current;
int node = p->node_last;
- WARN_ON_ONCE(p != container_of(work, struct task_struct, rcu));
+ WARN_ON_ONCE(p != container_of(work, struct task_struct, numa_work));
/*
* Who cares about NUMA placement when they're dying.
@@ -891,8 +891,8 @@ void task_tick_numa(struct rq *rq, struc
* yet and exit_task_work() is called before
* exit_notify().
*/
- init_task_work(&curr->rcu, task_numa_work);
- task_work_add(curr, &curr->rcu, true);
+ init_task_work(&curr->numa_work, task_numa_work);
+ task_work_add(curr, &curr->numa_work, true);
}
curr->node_last = node;
}
next prev parent reply other threads:[~2012-08-08 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 12:33 rcu stalls seen with numasched_v2 patches applied Srikar Dronamraju
2012-08-07 13:52 ` Peter Zijlstra
2012-08-07 17:19 ` Srikar Dronamraju
2012-08-08 19:58 ` Peter Zijlstra [this message]
2012-08-10 16:24 ` Srikar Dronamraju
2012-08-13 7:51 ` Peter Zijlstra
2012-08-13 8:11 ` Peter Zijlstra
2012-08-16 17:16 ` Srikar Dronamraju
2012-08-17 5:23 ` Srikar Dronamraju
2012-08-07 17:08 ` John Stultz
2012-08-07 16:59 ` Srikar Dronamraju
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=1344455938.16728.13.camel@laptop \
--to=peterz@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=srikar@linux.vnet.ibm.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.