From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/2] workqueue: Use normal rcu
Date: Fri, 22 Mar 2019 18:59:24 +0100 [thread overview]
Message-ID: <20190322175923.5o6y53yiseo3phif@linutronix.de> (raw)
In-Reply-To: <20190322174334.GC69236@devbig004.ftw2.facebook.com>
On 2019-03-22 10:43:34 [-0700], Tejun Heo wrote:
> Hello,
Hi,
> We can switch but it doesn't really say why we'd want to. Can you
> please explain why this is better?
there is this undocumented part. Avoiding the sched RCU means also we
are more preemptible which is good :) Especially on -RT where we can't
disable preemption across the whole critical section.
Is this good enough?
> Thanks.
Sebastian
next prev parent reply other threads:[~2019-03-22 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 16:55 [PATCH 0/2] workqueue: use normal RCU and don't depend on the rq lock Sebastian Andrzej Siewior
2019-03-13 16:55 ` [PATCH 1/2] workqueue: Use normal rcu Sebastian Andrzej Siewior
2019-03-21 20:59 ` Sebastian Andrzej Siewior
2019-03-22 17:43 ` Tejun Heo
2019-03-22 17:59 ` Sebastian Andrzej Siewior [this message]
2019-04-05 14:42 ` Sebastian Andrzej Siewior
2019-04-08 15:10 ` Tejun Heo
2019-04-08 19:38 ` Tejun Heo
2019-03-13 16:55 ` [PATCH 2/2] sched: Distangle worker accounting from rq lock Sebastian Andrzej Siewior
2019-04-08 19:45 ` Tejun Heo
2019-04-09 7:33 ` Sebastian Andrzej Siewior
2019-04-09 8:22 ` Peter Zijlstra
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=20190322175923.5o6y53yiseo3phif@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 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.