From: Tejun Heo <tj@kernel.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <frederic@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>, Phil Auld <pauld@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH v4 0/4] workqueue: destroy_worker() vs isolated CPUs
Date: Mon, 31 Oct 2022 08:45:20 -1000 [thread overview]
Message-ID: <Y2AXwPEqqaVi45g/@slm.duckdns.org> (raw)
In-Reply-To: <xhsmhfsfcw86h.mognet@vschneid.remote.csb>
On Tue, Oct 25, 2022 at 10:42:46AM +0100, Valentin Schneider wrote:
> On 04/10/22 16:05, Valentin Schneider wrote:
> > Hi folks,
> >
> > I haven't sent an update for this in a while, but the issue has risen again in
> > some other environment so I'm getting more reasons to push this out.
>
> Gentle ping.
The approach looks fine to me. I only have minor comments. I'll reply to
each patch.
Lai, you've been involved in this effort in earlier patch series, how does
this look to you now?
Thanks.
--
tejun
prev parent reply other threads:[~2022-10-31 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 15:05 [PATCH v4 0/4] workqueue: destroy_worker() vs isolated CPUs Valentin Schneider
2022-10-04 15:05 ` [PATCH v4 1/4] workqueue: Protects wq_unbound_cpumask with wq_pool_attach_mutex Valentin Schneider
2022-10-04 15:05 ` [PATCH v4 2/4] workqueue: Factorize unbind/rebind_workers() logic Valentin Schneider
2022-10-04 15:05 ` [PATCH v4 3/4] workqueue: Convert the idle_timer to a delayed_work Valentin Schneider
2022-10-31 18:49 ` Tejun Heo
2022-11-02 17:13 ` Valentin Schneider
2022-10-04 15:05 ` [PATCH v4 4/4] workqueue: Unbind workers before sending them to exit() Valentin Schneider
2022-10-05 1:08 ` Hillf Danton
2022-10-05 11:13 ` Valentin Schneider
2022-10-05 14:50 ` Hillf Danton
2022-10-05 16:14 ` Valentin Schneider
2022-10-06 2:07 ` Hillf Danton
2022-10-25 9:42 ` [PATCH v4 0/4] workqueue: destroy_worker() vs isolated CPUs Valentin Schneider
2022-10-31 18:45 ` Tejun Heo [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=Y2AXwPEqqaVi45g/@slm.duckdns.org \
--to=tj@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=vschneid@redhat.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.