From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] workqueue: Add a trace event for works enqueuing
Date: Mon, 4 Oct 2010 17:54:44 +0200 [thread overview]
Message-ID: <20101004155410.GA5381@nowhere> (raw)
In-Reply-To: <4CA9E8E0.7040503@kernel.org>
On Mon, Oct 04, 2010 at 04:46:56PM +0200, Tejun Heo wrote:
> Sorry about the delay. I was off last week.
>
> How about something like this? It probably needs to be split into two
> patches. It provides more information on which CPU was requested and
> eventually chosen and separates queueing and activation which can be
> useful for analyzing latency or freezer issues.
>
> Thanks.
Yep looks good. I hadn't thought about frozen works.
Thanks.
(I think this should go through your tree rather than the tracing tree).
next prev parent reply other threads:[~2010-10-04 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 15:39 [PATCH] workqueue: Add a trace event for works enqueuing Frederic Weisbecker
2010-10-04 14:46 ` Tejun Heo
2010-10-04 15:54 ` Frederic Weisbecker [this message]
2010-10-05 8:59 ` [PATCH wq#for-next 1/2] workqueue: prepare for more tracepoints Tejun Heo
2010-10-05 8:59 ` [PATCH wq#for-next 2/2] workqueue: add queue_work and activate_work trace points Tejun Heo
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=20101004155410.GA5381@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tj@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