From: Stefan Metzmacher <[email protected]>
To: Jens Axboe <[email protected]>,
Samba Technical <[email protected]>,
io-uring <[email protected]>
Subject: Re: Samba with multichannel and io_uring
Date: Fri, 16 Oct 2020 14:28:56 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
[-- Attachment #1.1: Type: text/plain, Size: 296 bytes --]
> 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
>
> ps and top still truncate, but that can be fixed.
I commented on https://gitlab.com/procps-ng/procps/-/issues/51
metze
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-16 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 9:58 Samba with multichannel and io_uring Stefan Metzmacher
2020-10-15 10:06 ` Ralph Boehme
2020-10-15 15:45 ` Jeremy Allison
2020-10-15 16:11 ` Jens Axboe
2020-10-16 11:49 ` Stefan Metzmacher
2020-10-16 12:28 ` Stefan Metzmacher [this message]
2020-10-16 12:40 ` Stefan Metzmacher
2020-10-16 18:56 ` Jens Axboe
2020-10-16 15:57 ` Jens Axboe
2020-10-16 16:03 ` Stefan Metzmacher
2020-10-16 16:06 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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