public inbox for linux-erofs@ozlabs.org
 help / color / mirror / Atom feed
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 v3] erofs-utils: lib: name worker threads erofs_compress
Date: Tue, 17 Mar 2026 01:05:41 +0800	[thread overview]
Message-ID: <5bf6079c-e66a-4c40-b6bf-f4abe961bc83@linux.alibaba.com> (raw)
In-Reply-To: <20260316170233.30662-1-nithurshen.dev@gmail.com>



On 2026/3/17 01:02, Nithurshen wrote:

..


> @@ -1427,6 +1430,12 @@ void *z_erofs_mt_wq_tls_alloc(struct erofs_workqueue *wq, void *ptr)
>   {
>   	struct erofs_compress_wq_tls *tls;
>   
> +#if defined(__linux__)
> +	prctl(PR_SET_NAME, "erofs_compress");
> +#elif defined(__APPLE__)
> +	pthread_setname_np("erofs_compress");
> +#endif

Why not call them as `erofs_compressor`?

and could we wrap it up as a new function like:

erofs_set_thread_name() somewhere instead so that
users can use it easier instead?

Thanks,
Gao Xiang

> +
>   	tls = calloc(1, sizeof(*tls));
>   	if (!tls)
>   		return NULL;



  reply	other threads:[~2026-03-16 17:05 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
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 [this message]
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=5bf6079c-e66a-4c40-b6bf-f4abe961bc83@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