From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
tglx@linutronix.de, tj@kernel.org
Subject: Re: [PATCH] srcu: Remove srcu_queue_delayed_work_on()
Date: Thu, 13 Dec 2018 07:26:53 -0800 [thread overview]
Message-ID: <20181213152653.GJ4170@linux.ibm.com> (raw)
In-Reply-To: <20181213150358.bgrwgpp5am5w53ie@linutronix.de>
On Thu, Dec 13, 2018 at 04:03:58PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-12-12 22:05:19 [+0800], Boqun Feng wrote:
> > So Jiangshan and TJ, what's your opion on this one? If we call a
> > queue_work_on() at a place where that target cpu may be offlined, I
> > think we have the guarantee that the work will be eventually executed
> > even if the cpu is never online again, right? In other words, if a cpu
> > has been online once, queue_work_on() on it will be free from racing
> > with cpu hotplug.
> >
> > Am I right about this, or did I miss something subtle?
>
> tj answered this one:
> https://lkml.kernel.org/r/20180919205521.GE902964@devbig004.ftw2.facebook.com
I must confess that I would have felt better about that email had it
been more definite than "is might just work already". ;-)
Thanx, Paul
prev parent reply other threads:[~2018-12-13 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 11:12 [PATCH] srcu: Remove srcu_queue_delayed_work_on() Sebastian Andrzej Siewior
2018-12-11 17:40 ` Paul E. McKenney
2018-12-12 1:40 ` Joel Fernandes
2018-12-12 14:05 ` Boqun Feng
2018-12-12 15:55 ` Paul E. McKenney
2018-12-13 1:36 ` Joel Fernandes
2018-12-13 15:06 ` Sebastian Andrzej Siewior
2018-12-13 15:03 ` Sebastian Andrzej Siewior
2018-12-13 15:26 ` Paul E. McKenney [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=20181213152653.GJ4170@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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