From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] Support optional performance counters, including congestion control performance counters.
Date: Wed, 20 Jul 2011 14:35:21 -0400 [thread overview]
Message-ID: <4E271FE9.7080508@dev.mellanox.co.il> (raw)
In-Reply-To: <1311183503.6898.153.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
Hi again Al,
On 7/20/2011 1:38 PM, Albert Chu wrote:
> Hey Hal,
>
> Thanks for the nit-catches. As for
>
>> + {32, 2, "PortVLXmitFlowCtlUpdateErrors0", mad_dump_uint},
>>> + {34, 2, "PortVLXmitFlowCtlUpdateErrors1", mad_dump_uint},
>>> + {36, 2, "PortVLXmitFlowCtlUpdateErrors2", mad_dump_uint},
>>> + {38, 2, "PortVLXmitFlowCtlUpdateErrors3", mad_dump_uint},
>>> + {40, 2, "PortVLXmitFlowCtlUpdateErrors4", mad_dump_uint},
>>> + {42, 2, "PortVLXmitFlowCtlUpdateErrors5", mad_dump_uint},
>>> + {44, 2, "PortVLXmitFlowCtlUpdateErrors6", mad_dump_uint},
>>> + {46, 2, "PortVLXmitFlowCtlUpdateErrors7", mad_dump_uint},
>>> + {48, 2, "PortVLXmitFlowCtlUpdateErrors8", mad_dump_uint},
>>> + {50, 2, "PortVLXmitFlowCtlUpdateErrors9", mad_dump_uint},
>>> + {52, 2, "PortVLXmitFlowCtlUpdateErrors10", mad_dump_uint},
>>> + {54, 2, "PortVLXmitFlowCtlUpdateErrors11", mad_dump_uint},
>>> + {56, 2, "PortVLXmitFlowCtlUpdateErrors12", mad_dump_uint},
>>> + {58, 2, "PortVLXmitFlowCtlUpdateErrors13", mad_dump_uint},
>>> + {60, 2, "PortVLXmitFlowCtlUpdateErrors14", mad_dump_uint},
>>> + {62, 2, "PortVLXmitFlowCtlUpdateErrors15", mad_dump_uint},
>>
>> Don't these need to be BITSOFFS(nn, 2) ?
>
> Perhaps there's a subtlety I'm missing. If these require BITSOFFS, then
> wouldn't the 16 bit fields require them too? There are many places
> amongst the performance counters that BITSOFFS isn't used w/ 16 bit
> fields.
Yes; it looks like any field less than 32 bits should use BITSOFFS so I
think that there are some existing things to fix in fields.c (the 16 bit
fields that are not using the macro).
-- Hal
> Al
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-20 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1311113629.6898.139.camel@auk59.llnl.gov>
[not found] ` <1311113629.6898.139.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-07-20 13:45 ` [PATCH] Support optional performance counters, including congestion control performance counters Hal Rosenstock
[not found] ` <4E26DBEF.1030205-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-20 17:38 ` Albert Chu
[not found] ` <1311183503.6898.153.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-07-20 18:35 ` Hal Rosenstock [this message]
[not found] ` <4E271FE9.7080508-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-07-21 0:04 ` Albert Chu
[not found] ` <1311206683.6898.184.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-07-22 0:20 ` Ira Weiny
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=4E271FE9.7080508@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=chu11-i2BcT+NCU+M@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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