From: Peter Zijlstra <peterz@infradead.org>
To: minyard@acm.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
Konstantin Baydarov <kbaidarov@ru.mvista.com>
Subject: Re: [PATCH 3/4] IPMI: convert locked counters to atomics
Date: Fri, 15 Feb 2008 14:57:23 +0100 [thread overview]
Message-ID: <1203083843.6855.44.camel@twins> (raw)
In-Reply-To: <20080214183051.GC20148@minyard.local>
On Thu, 2008-02-14 at 12:30 -0600, Corey Minyard wrote:
> +/*
> + * Various statistics for IPMI, these index stats[] in the ipmi_smi
> + * structure.
> + */
> +/* Commands we got from the user that were invalid. */
> +#define IPMI_STAT_sent_invalid_commands 0
> +
> +/* Commands we sent to the MC. */
> +#define IPMI_STAT_sent_local_commands 1
> +
> +/* Responses from the MC that were delivered to a user. */
> +#define IPMI_STAT_handled_local_responses 2
> +
> +/* Responses from the MC that were not delivered to a user. */
> +#define IPMI_STAT_unhandled_local_responses 3
> +
> +/* Commands we sent out to the IPMB bus. */
> +#define IPMI_STAT_sent_ipmb_commands 4
> +
> +/* Commands sent on the IPMB that had errors on the SEND CMD */
> +#define IPMI_STAT_sent_ipmb_command_errs 5
> +
> +/* Each retransmit increments this count. */
> +#define IPMI_STAT_retransmitted_ipmb_commands 6
> +
> +/* When a message times out (runs out of retransmits) this is incremented. */
> +#define IPMI_STAT_timed_out_ipmb_commands 7
> +
> +/*
> + * This is like above, but for broadcasts. Broadcasts are
> + * *not* included in the above count (they are expected to
> + * time out).
> + */
> +#define IPMI_STAT_timed_out_ipmb_broadcasts 8
> +
> +/* Responses I have sent to the IPMB bus. */
> +#define IPMI_STAT_sent_ipmb_responses 9
> +
> +/* The response was delivered to the user. */
> +#define IPMI_STAT_handled_ipmb_responses 10
> +
> +/* The response had invalid data in it. */
> +#define IPMI_STAT_invalid_ipmb_responses 11
> +
> +/* The response didn't have anyone waiting for it. */
> +#define IPMI_STAT_unhandled_ipmb_responses 12
> +
> +/* Commands we sent out to the IPMB bus. */
> +#define IPMI_STAT_sent_lan_commands 13
> +
> +/* Commands sent on the IPMB that had errors on the SEND CMD */
> +#define IPMI_STAT_sent_lan_command_errs 14
> +
> +/* Each retransmit increments this count. */
> +#define IPMI_STAT_retransmitted_lan_commands 15
> +
> +/* When a message times out (runs out of retransmits) this is incremented. */
> +#define IPMI_STAT_timed_out_lan_commands 16
> +
> +/* Responses I have sent to the IPMB bus. */
> +#define IPMI_STAT_sent_lan_responses 17
> +
> +/* The response was delivered to the user. */
> +#define IPMI_STAT_handled_lan_responses 18
> +
> +/* The response had invalid data in it. */
> +#define IPMI_STAT_invalid_lan_responses 19
> +
> +/* The response didn't have anyone waiting for it. */
> +#define IPMI_STAT_unhandled_lan_responses 20
> +
> +/* The command was delivered to the user. */
> +#define IPMI_STAT_handled_commands 21
> +
> +/* The command had invalid data in it. */
> +#define IPMI_STAT_invalid_commands 22
> +
> +/* The command didn't have anyone waiting for it. */
> +#define IPMI_STAT_unhandled_commands 23
> +
> +/* Invalid data in an event. */
> +#define IPMI_STAT_invalid_events 24
> +
> +/* Events that were received with the proper format. */
> +#define IPMI_STAT_events 25
> +
> +/* When you add a statistic, you must update this value. */
> +#define IPMI_NUM_STATS 26
This shouts enum to me..
next prev parent reply other threads:[~2008-02-15 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 18:30 [PATCH 3/4] IPMI: convert locked counters to atomics Corey Minyard
2008-02-14 19:11 ` Andrew Morton
2008-02-14 19:33 ` Corey Minyard
2008-02-14 20:23 ` Andrew Morton
2008-02-15 13:57 ` Peter Zijlstra [this message]
2008-02-15 14:08 ` [Openipmi-developer] " Corey Minyard
2008-02-16 16:44 ` Matt Domsch
2008-02-20 15:20 ` Corey Minyard
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=1203083843.6855.44.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@osdl.org \
--cc=kbaidarov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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.