From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Nithurshen <nithurshen.dev@gmail.com>, linux-erofs@lists.ozlabs.org
Cc: xiang@kernel.org
Subject: Re: [PATCH] erofs-utils: lib: name worker threads erofs_compress
Date: Tue, 17 Mar 2026 00:49:33 +0800 [thread overview]
Message-ID: <6edda81f-5d2e-49d0-9b31-181e3fdf0b18@linux.alibaba.com> (raw)
In-Reply-To: <20260316151352.59423-1-nithurshen.dev@gmail.com>
On 2026/3/16 23:13, Nithurshen wrote:
> Set a specific thread name for the multi-threaded workqueue workers
> to make debugging, profiling, and process monitoring significantly
> easier.
>
> Previously, worker threads inherited the name of the parent process
> (e.g., mkfs.erofs), making it difficult to distinguish them from the
> main thread in tools like \`top\`, \`htop\`, or \`ps\`.
Please just use `top`, `htop`, or `ps` here.
>
> This utilizes \`prctl(PR_SET_NAME)\` on Linux and \`pthread_setname_np\`
> on macOS to explicitly label these threads as \"erofs_compress\" upon
> initialization.
Why not just calling erofs_compressor, since those worker are really
compressor.
>
> Signed-off-by: Nithurshen <nithurshen.dev@gmail.com>
> ---
> lib/workqueue.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/lib/workqueue.c b/lib/workqueue.c
> index 18ee0f9..860e403 100644
> --- a/lib/workqueue.c
> +++ b/lib/workqueue.c
> @@ -2,6 +2,9 @@
> #include <pthread.h>
> #include <stdlib.h>
> #include "erofs/workqueue.h"
> +#if defined(__linux__)
> +#include <sys/prctl.h>
> +#endif
>
> static void *worker_thread(void *arg)
> {
> @@ -9,6 +12,12 @@ static void *worker_thread(void *arg)
> struct erofs_work *work;
> void *tlsp = NULL;
>
> +#if defined(__linux__)
> + prctl(PR_SET_NAME, "erofs_compress");
> +#elif defined(__APPLE__)
> + pthread_setname_np("erofs_compress");
> +#endif
I don't think they should be added here, you could
add in .on_start() of lib/compress.c instead.
Thanks,
Gao Xiang
> +
> if (wq->on_start)
> tlsp = (wq->on_start)(wq, NULL);
>
next prev parent reply other threads:[~2026-03-16 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 15:13 [PATCH] erofs-utils: lib: name worker threads erofs_compress Nithurshen
2026-03-16 16:49 ` Gao Xiang [this message]
2026-03-16 16:54 ` [PATCH v2] " Nithurshen
2026-03-16 17:00 ` Gao Xiang
2026-03-16 17:02 ` [PATCH v3] " Nithurshen
2026-03-16 17:05 ` Gao Xiang
2026-03-16 17:11 ` [PATCH] " Nithurshen Karthikeyan
2026-03-16 17:15 ` Gao Xiang
2026-03-16 17:25 ` [PATCH v4] erofs-utils: lib: name worker threads erofscompressor Nithurshen
2026-03-16 17:58 ` Gao Xiang
2026-03-16 18:01 ` [PATCH v5] " Nithurshen
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=6edda81f-5d2e-49d0-9b31-181e3fdf0b18@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=nithurshen.dev@gmail.com \
--cc=xiang@kernel.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