All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] SUNRPC: Adding status trace points
Date: Mon, 06 Feb 2012 12:30:05 -0500	[thread overview]
Message-ID: <4F300E1D.6050104@RedHat.com> (raw)
In-Reply-To: <1328542771.5687.1.camel@lade.trondhjem.org>



On 02/06/2012 10:39 AM, Myklebust, Trond wrote:
> On Mon, 2012-02-06 at 10:08 -0500, Steve Dickson wrote:
>> This patch adds three trace points to the status routines
>> in the sunrpc state machine.
>>
>> The goal of these trace points is to give an Admin
>> the ability to check on binding status or connection
>> status to see if there is a potential problem.
>>
>> Signed-off-by: Steve Dickson <steved@redhat.com>
>> ---
>>  include/trace/events/sunrpc.h |   53 +++++++++++++++++++++++++++++++++++++++++
>>  net/sunrpc/clnt.c             |    6 ++++-
>>  2 files changed, 58 insertions(+), 1 deletions(-)
>>
>> diff --git a/include/trace/events/sunrpc.h b/include/trace/events/sunrpc.h
>> index 2f82de9..abcf45d 100644
>> --- a/include/trace/events/sunrpc.h
>> +++ b/include/trace/events/sunrpc.h
>> @@ -8,6 +8,59 @@
>>  #include <linux/sunrpc/clnt.h>
>>  #include <linux/tracepoint.h>
>>  
>> +DECLARE_EVENT_CLASS(rpc_task_status,
>> +
>> +	TP_PROTO(struct rpc_task *task),
>> +
>> +	TP_ARGS(task),
>> +
>> +	TP_STRUCT__entry(
>> +		__field(const struct rpc_task *, task)
>> +		__field(const struct rpc_clnt *, clnt)
>> +		__field(int, status)
>> +	),
>> +
>> +	TP_fast_assign(
>> +		__entry->task = task;
>> +		__entry->clnt = task->tk_client;
>> +		__entry->status = task->tk_status;
>> +	),
>> +
>> +	TP_printk("task:%p@%p, status %d",__entry->task, __entry->clnt, __entry->status)
>> +);
>> +
>> +DEFINE_EVENT(rpc_task_status, rpc_call_status,
>> +	TP_PROTO(struct rpc_task *task), 
>> +
>> +	TP_ARGS(task)
>> +);
>> +
>> +DEFINE_EVENT(rpc_task_status, rpc_bind_status,
>> +	TP_PROTO(struct rpc_task *task), 
>> +
>> +	TP_ARGS(task)
>> +);
>> +
>> +TRACE_EVENT(rpc_connect_status,
>> +	TP_PROTO(struct rpc_task *task, int status),
>> +
>> +	TP_ARGS(task, status),
>> +
>> +	TP_STRUCT__entry(
>> +		__field(const struct rpc_task *, task)
>> +		__field(const struct rpc_clnt *, clnt)
>> +		__field(int, status)
>> +	),
>> +
>> +	TP_fast_assign(
>> +		__entry->task = task;
>> +		__entry->clnt = task->tk_client;
>> +		__entry->status = status;
>> +	),
>> +
>> +	TP_printk("task:%p@%p, status %d",__entry->task, __entry->clnt, __entry->status)
>> +);
>> +
>>  DECLARE_EVENT_CLASS(rpc_task_running,
>>  
> 
> 
> This hunk did contain a couple of trailing whitespace errors, but I've
> fixed them up and applied.
Hmm... Sorry about... I wonder how that happen... any ways thanks!

steved.

      reply	other threads:[~2012-02-06 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:08 [PATCH v3 0/2] SUNRPC: Added Tracing Points Steve Dickson
2012-02-06 15:08 ` [PATCH v3 1/2] SUNRPC: Add trace events to the sunrpc subsystem Steve Dickson
2012-02-06 17:47   ` Christoph Hellwig
2012-02-06 18:21     ` Myklebust, Trond
2012-02-06 15:08 ` [PATCH v3 2/2] SUNRPC: Adding status trace points Steve Dickson
2012-02-06 15:39   ` Myklebust, Trond
2012-02-06 17:30     ` Steve Dickson [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=4F300E1D.6050104@RedHat.com \
    --to=steved@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.