linux-kernel - Re: [PATCH 0/4] workqueue_tracepoint: Add worklet tracepoints for worklet lifecycle tracing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090424130616.a3c217cb.akpm@linux-foundation.org>
Date:	Fri, 24 Apr 2009 13:06:16 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Zhaolei <zhaolei@...fujitsu.com>
Cc:	mingo@...e.hu, kosaki.motohiro@...fujitsu.com, fweisbec@...il.com,
	rostedt@...dmis.org, tzanussi@...il.com,
	linux-kernel@...r.kernel.org, oleg@...hat.com
Subject: Re: [PATCH 0/4] workqueue_tracepoint: Add worklet tracepoints for
 worklet lifecycle tracing

On Fri, 24 Apr 2009 19:42:19 +0800
Zhaolei <zhaolei@...fujitsu.com> wrote:

> These patchs add tracepoints for per-worklet tracing.
> Now we have enough tracepoints to start makeing trace_workqueue.c support
> worklet time mesurement.

I'm not seing anywhere in this patchset a description of the user
interface.  What does the operator/programmer actually get to see from
the kernel as a result of these changes?

A complete usage example would be an appropriate way of communicating
all of this.

The patches introduce a moderate amount of tracing-specific hooks into
the core workqueue code, which inevitably increases the maintenance
load for that code.  It is important that it be demonstrated that the
benefts of the code are worth that cost.  Hence it is important that
these benefits be demonstrated to us, by yourself.  Please.

Another way of looking at it: which previously-encountered problems
would this facility have helped us to solve?  How will this facility
help us to solve problems in the future?  Looking at this patch series
I cannot answer those questions!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/