From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Subject: Re: [Patch infiniband-diags:perfquery] Loop through all local HCAs/ports
Date: Sat, 30 Jul 2011 10:11:16 -0400 [thread overview]
Message-ID: <4E341104.90105@redhat.com> (raw)
In-Reply-To: <20110729222612.GM18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
On 7/29/2011 6:26 PM, Jason Gunthorpe wrote:
>>> Not sure what I think of this, is dumping counters on all local HCA
>>> ports really that interesting? Would this be better done by doing
>>> something fancy with nodeGUID so at least all ports on remote HCAs can
>>> be dumped too?
>>
>> The request came in from one of our partners who wanted it for
>> tracking performance stats specifically on the local machine.
>
> Well, I think it would be best to make this work generally which is
> fairly hard, unfortunately.
> - If the destination is the local HCA then you have to iterate over
> all local ports with matching node GUIDs by opening devices
> - If the destination is a remote HCA then you have to query the SA
> for all nodes with a matching GUID and iterate over them. Ira has
> been working on some common code for this..
> - Maybe you want to cross product and try to query the SA attached to
> all local end ports to try and find all ports. That would actually be
> very useful for many situations I know of...
>
> Could you make your patch just do #1 and continue to misbehave for
> the other cases?
Well, it sort of already does. The patch looks bigger than it is
because I had to re-indent in order to put the main functional code
inside of a loop. For the most part, the loop is unchanged. Just apply
the patch then look at what we do when all_hcas is non-0 right before
the do { and right before the } while (ibd_ca); It iterates over all
the hca names that libibumad gives us, and then loops over all the ports
as returned by libibumad's umad_get_ca().
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2011-07-30 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 21:57 [Patch infiniband-diags:perfquery] Loop through all local HCAs/ports Doug Ledford
[not found] ` <4E332CE5.3010706-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-29 22:04 ` Doug Ledford
2011-07-29 22:09 ` Jason Gunthorpe
[not found] ` <20110729220912.GL18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-07-29 22:14 ` Doug Ledford
[not found] ` <4E3330AF.9050208-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-29 22:26 ` Jason Gunthorpe
[not found] ` <20110729222612.GM18090-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-07-30 14:11 ` Doug Ledford [this message]
[not found] ` <4E341104.90105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-10 0:56 ` 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=4E341104.90105@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@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