On 10/16/20 10:03 AM, Stefan Metzmacher wrote: >> >> I don't think that's too important, as it's just a snapshot in time. So >> it'll fluctuate based on the role of the worker. >> >>> I just found that proc_task_name() handles PF_WQ_WORKER special >>> and cat /proc/$pid/comm can expose something like: >>> kworker/u17:2-btrfs-worker-high >> >> Yep, that's how they do fancier names. It's been on my agenda for a while >> to do something about this, I'll try and cook something up for 5.11. > > With a function like wq_worker_comm being called by proc_task_name(), > you would capture current IO_WORKER_F_BOUND state and alter the name. Oh yes, it'll be accurate enough, my point is just that by the time you see it, reality might be different. But that's fine, that's how they work. > Please CC me on your patches in that direction. Will do! -- Jens Axboe
