[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4VZsFBn13nBnGjb@slm.duckdns.org>
Date: Mon, 13 Jan 2025 08:21:36 -1000
From: Tejun Heo <tj@...nel.org>
To: Imran Khan <imran.f.khan@...cle.com>
Cc: jiangshanlai@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] workqueue: introduce
queue_delayed_work_on_offline_safe.
On Mon, Jan 13, 2025 at 03:35:40PM +1100, Imran Khan wrote:
...
> I have kept the patch as RFC because from mailing list,
> I could not find any users, of queue_delayed_work_on,
> that is ending up queuing dwork on an offlined CPU.
> We have some in-house code that is running into this problem,
> and currently we are fixing it on caller side of queue_delayed_work_on.
> Other users who run into this issue, can also use the approach of
> fixing it on caller side or we can use the interface introduced
> here for such use cases.
I'm not sure how necessary this is. If the timer is okay to run on other
CPUs, might as well just use queue_delayed_work().
Thanks.
--
tejun
Powered by blists - more mailing lists