From: Jens Axboe <axboe@kernel.dk>
To: Stefan Metzmacher <metze@samba.org>,
Samba Technical <samba-technical@lists.samba.org>,
io-uring <io-uring@vger.kernel.org>
Subject: Re: Samba with multichannel and io_uring
Date: Fri, 16 Oct 2020 10:06:24 -0600 [thread overview]
Message-ID: <461e4fc4-0e7d-2a6f-f2eb-a962b077ed81@kernel.dk> (raw)
In-Reply-To: <892e855a-9c4f-ea5b-6728-f02df271c2c8@samba.org>
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
prev parent reply other threads:[~2020-10-16 16:06 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
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 [this message]
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=461e4fc4-0e7d-2a6f-f2eb-a962b077ed81@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.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;
as well as URLs for NNTP newsgroup(s).