From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: Eric Wheeler <drbd-dev@lists.ewheeler.net>
Cc: drbd-dev@lists.linbit.com, Eric Wheeler <git@linux.ewheeler.net>,
Eric Wheeler <drbd@linux.ewheeler.net>,
Philipp Reisner <philipp.reisner@linbit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drbd: standardize kthread/workqueue thread naming to include drbd minor number
Date: Tue, 16 Jan 2018 10:08:09 +0100 [thread overview]
Message-ID: <20180116090809.GC4107@soda.linbit> (raw)
In-Reply-To: <1516060335-27029-1-git-send-email-drbd-dev@lists.ewheeler.net>
On Mon, Jan 15, 2018 at 03:52:15PM -0800, Eric Wheeler wrote:
> From: Eric Wheeler <git@linux.ewheeler.net>
>
> For DRBD resources with long names that start with the same prefix,
> it was difficult to find all process pids for that minor since names
> are truncated to the task_struct's comm field (16 bytes).
>
> This patch names all processes associated with a DRBD device as drbdN_*
> where N is the DRBD minor in the same ways that the drbdN_submit workqueue
> is named. Userspace tools can then lookup the name=>minor=>pid mapping
> and for all pids and use tools like chrt, ioprio, nice, add pids to
> cgroups, or for other useful purpose.
DRBD can do "multi volume" resources, which means most threads
are associated not with one, but with many minors.
"does not work just like that"
Lars
prev parent reply other threads:[~2018-01-16 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 23:52 [PATCH] drbd: standardize kthread/workqueue thread naming to include drbd minor number Eric Wheeler
2018-01-16 9:08 ` Lars Ellenberg [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=20180116090809.GC4107@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.ewheeler.net \
--cc=drbd-dev@lists.linbit.com \
--cc=drbd@linux.ewheeler.net \
--cc=git@linux.ewheeler.net \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
/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