Messages in this thread | | | From | Aaron Tomlin <> | Subject | Re: [RFC PATCH 0/2] workqueue: Introduce PF_WQ_RESCUE_WORKER | Date | Thu, 3 Aug 2023 21:19:14 +0100 |
| |
> But why do you need to identify rescue workers? What are you trying to > achieve?
Hi Tejun,
I had a conversation with a colleague of mine. It can be useful to identify and account for all kernel threads. From the perspective of user-mode, the name given currently to the rescuer kworker is ambiguous. For instance, "kworker/u16:9-kcryptd/253:0" is clearly identifiable as an unbound kworker for the specified workqueue which can have their CPU affinity adjusted as you mentioned before. I think if we followed the same naming convention for a rescuer kworker then it would be more consistent. I'll send a patch so it can be discussed further.
Kind regards, -- Aaron Tomlin
| |