From: brookxu <brookxu.cn@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: adobriyan@gmail.com, bsingharora@gmail.com,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] delayacct: add a proc file to dump the delay info
Date: Tue, 11 May 2021 09:10:21 +0800 [thread overview]
Message-ID: <b83bd36b-2e19-50f1-323b-2961a35bfe5e@gmail.com> (raw)
In-Reply-To: <20210509205853.42a3a06f9c5b70b52bdf8509@linux-foundation.org>
Thanks for you reply :)
Andrew Morton wrote on 2021/5/10 11:58:
> On Mon, 19 Apr 2021 22:37:07 +0800 brookxu <brookxu.cn@gmail.com> wrote:
>
>> Many distributions do not install the getdelay tool by
>> default, similar to task_io_accounting, adding a proc
>> file to make access easier.
>
> Well, we developed and maintain getdelays.c for a reason. Why should
> we add (and maintain) kernel code because some people are too
> lame to install the tool we provided?
>
In some production environments, all modifications are restricted, and
the addition of business-unrelated tools is generally not allowed.
Adding new tools to Linux distributions may require a very complicated
process, as some of them are directly using centos. But kernel upgrade
is sometimes necessary, so I think a proc file can circumvent many
problems in the production environment.
prev parent reply other threads:[~2021-05-11 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 14:37 [PATCH v2 1/2] delayacct: refactor the code to simplify the implementation brookxu
2021-04-19 14:37 ` [PATCH v2 2/2] delayacct: add a proc file to dump the delay info brookxu
2021-05-10 3:58 ` Andrew Morton
2021-05-10 8:48 ` Balbir Singh
2021-05-11 1:10 ` brookxu [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=b83bd36b-2e19-50f1-323b-2961a35bfe5e@gmail.com \
--to=brookxu.cn@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).