From: Tejun Heo <tj@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/3] workqueue: Make the workqueue code PREEMPT_RT safe
Date: Tue, 26 May 2020 15:46:41 -0400 [thread overview]
Message-ID: <20200526194641.GF83516@mtj.thefacebook.com> (raw)
In-Reply-To: <20200513162732.977489-1-bigeasy@linutronix.de>
Hello,
On Wed, May 13, 2020 at 06:27:29PM +0200, Sebastian Andrzej Siewior wrote:
> The series changes `wq_manager_wait' from waitqueues to simple
> waitqueues and its internal locking (pool::lock and wq_mayday_lock) to
> raw spinlocks so that workqueues can be used on PREEMPT_RT from truly
> atomic context.
No objection from workqueue side but the comment in swait.h doesn't look too
encouraging. Kinda difficult to make a call from my side. Linus, does this
qualify as the RT use case you had on mind?
Thanks.
--
tejun
next prev parent reply other threads:[~2020-05-26 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 16:27 [PATCH 0/3] workqueue: Make the workqueue code PREEMPT_RT safe Sebastian Andrzej Siewior
2020-05-13 16:27 ` [PATCH 1/3] sched/swait: Add swait_event_lock_irq() Sebastian Andrzej Siewior
2020-05-13 16:27 ` [PATCH 2/3] workqueue: Use swait for wq_manager_wait Sebastian Andrzej Siewior
2020-05-13 16:27 ` [PATCH 3/3] workqueue: Convert the pool::lock and wq_mayday_lock to raw_spinlock_t Sebastian Andrzej Siewior
2020-05-26 19:46 ` Tejun Heo [this message]
2020-05-26 21:41 ` [PATCH 0/3] workqueue: Make the workqueue code PREEMPT_RT safe Linus Torvalds
2020-05-26 21:46 ` Linus Torvalds
2020-05-27 15:20 ` Sebastian Andrzej Siewior
2020-05-27 15:52 ` Linus Torvalds
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=20200526194641.GF83516@mtj.thefacebook.com \
--to=tj@kernel.org \
--cc=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=torvalds@linux-foundation.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