From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] infiniband-diags: saquery; reuse dump_one_mcmember_record function
Date: Thu, 16 Jun 2011 14:46:36 -0700 [thread overview]
Message-ID: <20110616144636.4d2483fb.weiny2@llnl.gov> (raw)
In-Reply-To: <4DFA6D60.9070609-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On Thu, 16 Jun 2011 13:53:52 -0700
Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> wrote:
> On 6/16/2011 2:10 PM, Ira Weiny wrote:
> > - printf("MCMemberRecord member dump:\n"
> > - "\t\tMGID....................%s\n"
> > - "\t\tMlid....................0x%X\n"
> > - "\t\tPortGid.................%s\n"
> > - "\t\tScopeState..............0x%X\n"
> > - "\t\tProxyJoin...............0x%X\n"
> > - "\t\tNodeDescription.........%s\n",
> > - inet_ntop(AF_INET6, p_mcmr->mgid.raw, gid_str,
> > - sizeof gid_str),
> > - cl_ntoh16(p_mcmr->mlid),
> > - inet_ntop(AF_INET6, p_mcmr->port_gid.raw,
> > - gid_str2, sizeof gid_str2),
> > - p_mcmr->scope_state, p_mcmr->proxy_join, node_name);
> > + dump_one_mcmember_record(data);
>
> This will print more info per MC member with much of it (group related)
> repeated. Is there some need for the additional info or is this just for
> code reuse ?
"need"; I guess not. But I thought it was odd that the information was different for the 2 query methods. There is nothing in the documentation or help output which indicates the output would be different.
That said I do see what you mean regarding the amount of data returned. I figured most users were probably grepping this output anyway, as on a large fabric both methods return a sizable amount of data.
> If it's the latter, I would prefer to not see it change or
> add an additional parameter to dump_one_mcmember_record as to the
> specific fields to print.
Yea, the most useful output of "-m" is when used with the optional MLID value.
Ok, For now I will reject the patch. ;-)
Ira
>
> -- Hal
>
> > + printf("\t\tNodeDescription.........%s\n", node_nam
>
--
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org
--
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-06-16 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 18:10 [PATCH] infiniband-diags: saquery; reuse dump_one_mcmember_record function Ira Weiny
[not found] ` <20110616111024.fde795bc.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-06-16 20:53 ` Hal Rosenstock
[not found] ` <4DFA6D60.9070609-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2011-06-16 21:46 ` Ira Weiny [this message]
[not found] ` <20110616144636.4d2483fb.weiny2-i2BcT+NCU+M@public.gmane.org>
2011-06-16 21:59 ` Jason Gunthorpe
[not found] ` <20110616215946.GA7112-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-06-16 22:48 ` 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=20110616144636.4d2483fb.weiny2@llnl.gov \
--to=weiny2-i2bct+ncu+m@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@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