From: Andy Lutomirski <luto@amacapital.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
nicolas.pitre@linaro.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/8] sched,idle: need resched polling rework
Date: Tue, 3 Jun 2014 09:05:03 -0700 [thread overview]
Message-ID: <CALCETrW3cr_RLnMeMtutM5H+3cJSerUxXuEmiT9miDOEmkpANw@mail.gmail.com> (raw)
In-Reply-To: <20140603140223.GA13658@twins.programming.kicks-ass.net>
On Tue, Jun 3, 2014 at 7:02 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Jun 03, 2014 at 12:43:47PM +0200, Peter Zijlstra wrote:
>> We need rq->curr, rq->idle 'sleeps' with polling set and nr clear, but
>> it obviously has no effect setting that if its not actually the current
>> task.
>>
>> Touching rq->curr needs holding rcu_read_lock() though, to make sure the
>> task stays around, still shouldn't be a problem.
>
>> @@ -1581,8 +1604,14 @@ void scheduler_ipi(void)
>>
>> static void ttwu_queue_remote(struct task_struct *p, int cpu)
>> {
>> - if (llist_add(&p->wake_entry, &cpu_rq(cpu)->wake_list))
>> - smp_send_reschedule(cpu);
>> + struct rq *rq = cpu_rq(cpu);
>> +
>> + if (llist_add(&p->wake_entry, &rq->wake_list)) {
>> + rcu_read_lock();
>> + if (!set_nr_if_polling(rq->curr))
>> + smp_send_reschedule(cpu);
>> + rcu_read_unlock();
>> + }
>> }
>
> Hrmm, I think that is still broken, see how in schedule() we clear NR
> before setting the new ->curr.
>
> So I think I had a loop on rq->curr the last time we talked about this,
> but alternatively we could look at clearing NR after setting a new curr.
>
> I think I once looked at why it was done before, of course I can't
> actually remember the details :/
Wouldn't this be a little simpler and maybe even faster if we just
changed the idle loop to make TIF_POLLING_NRFLAG be a real indication
that the idle task is running and actively polling? That is, change
the end of cpuidle_idle_loop to:
preempt_set_need_resched();
tick_nohz_idle_exit();
clear_tsk_need_resched(current);
__current_clr_polling();
smp_mb__after_clear_bit();
WARN_ON_ONCE(test_thread_flag(TIF_POLLING_NRFLAG));
sched_ttwu_pending();
schedule_preempt_disabled();
__current_set_polling();
This has the added benefit that the optimistic version of the cmpxchg
loop would be safe again. I'm about to test this with this variant.
I'll try and send a comprehensible set of patches in a few hours.
Can you remind me what the benefit was of letting polling be set when
the idle thread schedules? It seems racy to me: it probably prevents
any safe use of the polling bit without holding the rq lock. I guess
there's some benefit to having polling be set for as long as possible,
but it only helps if there are wakeups in very rapid succession, and
it costs a couple of extra bit ops per idle entry.
--
Andy Lutomirski
AMA Capital Management, LLC
next prev parent reply other threads:[~2014-06-03 16:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 13:42 [RFC][PATCH 0/8] sched,idle: need resched polling rework Peter Zijlstra
2014-04-11 13:42 ` [RFC][PATCH 1/8] sched,idle,alpha: Switch from TS_POLLING to TIF_POLLING_NRFLAG Peter Zijlstra
2014-04-11 14:38 ` Richard Henderson
2014-04-11 13:42 ` [RFC][PATCH 2/8] sched,idle,tile: " Peter Zijlstra
2014-04-11 15:15 ` Chris Metcalf
2014-04-11 15:30 ` Peter Zijlstra
2014-04-11 13:42 ` [RFC][PATCH 3/8] sched,idle,ia64: " Peter Zijlstra
2014-04-11 13:42 ` [RFC][PATCH 4/8] sched,idle,x86: " Peter Zijlstra
2014-04-11 13:42 ` [RFC][PATCH 5/8] sched,idle: Remove TS_POLLING support Peter Zijlstra
2014-04-11 13:42 ` [RFC][PATCH 6/8] sched,idle: Avoid spurious wakeup IPIs Peter Zijlstra
2014-04-13 21:41 ` Nicolas Pitre
2014-05-09 13:37 ` James Hogan
2014-05-09 14:15 ` Peter Zijlstra
2014-05-09 14:40 ` Catalin Marinas
2014-05-09 14:50 ` Peter Zijlstra
2014-05-09 14:57 ` Catalin Marinas
2014-05-09 17:02 ` Peter Zijlstra
2014-05-09 17:06 ` Peter Zijlstra
2014-05-09 17:09 ` Catalin Marinas
2014-05-09 17:20 ` Peter Zijlstra
2014-05-19 12:54 ` [tip:sched/arch] arm64: Remove TIF_POLLING_NRFLAG tip-bot for Peter Zijlstra
2014-05-22 12:26 ` [tip:sched/core] " tip-bot for Peter Zijlstra
2014-05-09 14:51 ` [RFC][PATCH 6/8] sched,idle: Avoid spurious wakeup IPIs James Hogan
2014-05-15 9:17 ` James Hogan
2014-05-19 12:54 ` [tip:sched/arch] metag: Remove TIF_POLLING_NRFLAG tip-bot for James Hogan
2014-05-22 12:26 ` [tip:sched/core] " tip-bot for James Hogan
2014-04-11 13:42 ` [RFC][PATCH 7/8] sched,idle: Delay clearing the polling bit Peter Zijlstra
2014-04-13 21:51 ` Nicolas Pitre
2014-04-11 13:42 ` [RFC][PATCH 8/8] sched,idle: Reflow cpuidle_idle_call() Peter Zijlstra
2014-04-13 21:36 ` Nicolas Pitre
2014-04-14 8:59 ` Peter Zijlstra
2014-04-14 9:25 ` Peter Zijlstra
2014-04-14 13:55 ` Nicolas Pitre
2014-04-11 15:00 ` [RFC][PATCH 0/8] sched,idle: need resched polling rework Andy Lutomirski
2014-04-11 15:14 ` Peter Zijlstra
2014-05-22 12:58 ` Peter Zijlstra
2014-05-22 13:09 ` Peter Zijlstra
2014-05-29 0:01 ` Andy Lutomirski
2014-05-29 6:48 ` Peter Zijlstra
2014-06-03 6:40 ` Andy Lutomirski
2014-06-03 6:51 ` Peter Zijlstra
2014-06-03 10:43 ` Peter Zijlstra
2014-06-03 14:02 ` Peter Zijlstra
2014-06-03 16:05 ` Andy Lutomirski [this message]
2014-06-03 16:19 ` Peter Zijlstra
2014-06-03 16:52 ` Andy Lutomirski
2014-06-03 17:00 ` Peter Zijlstra
2014-06-03 18:28 ` Peter Zijlstra
2014-06-03 18:44 ` Andy Lutomirski
2014-06-03 20:07 ` Andy Lutomirski
2014-04-12 8:35 ` Mike Galbraith
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=CALCETrW3cr_RLnMeMtutM5H+3cJSerUxXuEmiT9miDOEmkpANw@mail.gmail.com \
--to=luto@amacapital.net \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.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;
as well as URLs for NNTP newsgroup(s).