From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Nithurshen Karthikeyan <nithurshen.dev@gmail.com>
Cc: linux-erofs@lists.ozlabs.org, xiang@kernel.org
Subject: Re: [PATCH] erofs-utils: lib: name worker threads erofs_compress
Date: Tue, 17 Mar 2026 01:15:53 +0800 [thread overview]
Message-ID: <7e85a4c2-95a9-4ded-be83-97ceb7d707a6@linux.alibaba.com> (raw)
In-Reply-To: <CANRYsKivDEJojD3xgLcL5+jmmA3X-YcFpF-mweN5ef=eMhL-Qw@mail.gmail.com>
Hi Nithurshen,
On 2026/3/17 01:11, Nithurshen Karthikeyan wrote:
> Hi Xiang,
>
...
>>
>> Why not just calling erofs_compressor, since those worker are really
>> compressor.
>
> I initially tested using "erofs_compressor", but the OS thread naming
> API (`prctl` with `PR_SET_NAME`) has a strict 16-byte limit,
> which includes the null terminator.
>
> Because "erofs_compressor" is exactly 16 characters long, the null
> byte pushes it to 17 bytes. As a result, the kernel truncates it, and
> it actually shows up as "erofs_compresso" in `ps` and `top`.
>
> To keep the output looking clean and intentional, I chose to use
> "erofs_compress" (14 chars) instead. Please let me know if you are
> okay with this, or if you'd prefer a different abbreviation.
Ok, or just call it as `erofscompressor`?
`erofs_compress` is really awkward to me.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-03-16 17:16 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
2026-03-16 17:11 ` [PATCH] " Nithurshen Karthikeyan
2026-03-16 17:15 ` Gao Xiang [this message]
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=7e85a4c2-95a9-4ded-be83-97ceb7d707a6@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