All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kluge <Michael.Kluge@tu-dresden.de>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre RPC visualization
Date: Thu, 24 Jun 2010 10:01:14 +0200	[thread overview]
Message-ID: <44E9F0A8-5850-4FAA-992C-2C57D4F54AEE@tu-dresden.de> (raw)
In-Reply-To: <3BF1EC13-3865-41C8-B860-E190EF0DE876@oracle.com>

> While Alexey's comment is correct, in that there can be multiple Lustre client mounts on a single node, this is generally only used for testing.  For client connections the UUID is just a random value like "f4726b1e-f7eb-479f-b163-784ea45adf32", so using the NID is much more useful to the viewer in the vast majority of cases.

Well, what I can do with OTF and Vampir is to use a process hierarchy. So for each NID I can have a couple of UUID as 'child processes'. Like the way one looks at hybrid MPI & OpenMP programs. Where we have MPI processes and treat OpenMP threads as child processes.

> If you wanted to distinguish the multiple mounts from a single client it would be best to just do this internally by tracking both the NID and the UUID, but only printing the NID on the output.  For the rare case where requests have the same NID but a different UUID you could show this as "NID:2", "NID:3" or similar.  That preserves the distinction between client connections, while not making the output completely useless.

Yes, that fits into the statement above.

> Even better than plain numeric NIDs would be to do IP->hostname conversion for the case of TCP and IB LNDs, if this works.

Well, typically I only have the debug log. Which might be incomplete. I don't think I have something that can do this conversion reliably?


Michael


>> Am 23.06.2010 um 12:29 schrieb Alexey Lyashkov:
>> 
>>> I think better to use client UUID instead of NID as client identification. Because in your's case - you can't separate info from two clients which run on same node.
>>> 
>>> 
>>> On Jun 22, 2010, at 19:12, Michael Kluge wrote:
>>> 
>>>> The remaining problems of the counter calculations have been fixed. There is a screenshot attached showing some values. The code is in a gforge server that we operate here in Dresden (gforge.zih.tu-dresden.de). The converter runs on Linux and on MAC OS X and you need Vampir to take a look at the OTF trace file.
>>>> 
>>>> Eric, Galen, for the moment I think I am done with the stuff I promised you at LUG this year? Are there any more ideas?
>>>> 
>>>> 
>>>> Michael
>>>> 
>>>> 
>>>> 
>>>> <lustre3.png>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>>> 
>>> 
>>> 
>>> --------------------------------------
>>> Alexey Lyashkov
>>> alexey.lyashkov at clusterstor.com
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -- 
>> 
>> Michael Kluge, M.Sc.
>> 
>> Technische Universit?t Dresden
>> Center for Information Services and
>> High Performance Computing (ZIH)
>> D-01062 Dresden
>> Germany
>> 
>> Contact:
>> Willersbau, Room WIL A 208
>> Phone:  (+49) 351 463-34217
>> Fax:    (+49) 351 463-37773
>> e-mail: michael.kluge at tu-dresden.de
>> WWW:    http://www.tu-dresden.de/zih
>> 
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel
> 
> 
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Technical Lead
> Oracle Corporation Canada Inc.
> 
> 


-- 

Michael Kluge, M.Sc.

Technische Universit?t Dresden
Center for Information Services and
High Performance Computing (ZIH)
D-01062 Dresden
Germany

Contact:
Willersbau, Room WIL A 208
Phone:  (+49) 351 463-34217
Fax:    (+49) 351 463-37773
e-mail: michael.kluge at tu-dresden.de
WWW:    http://www.tu-dresden.de/zih

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20100624/77e1f513/attachment.htm>

  reply	other threads:[~2010-06-24  8:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000c01cae6ee$1d4693d0$57d3bb70$@barton@oracle.com>
2010-04-29  1:25 ` [Lustre-devel] (no subject) di.wang
2010-04-29  1:49   ` Andreas Dilger
2010-04-29  2:04     ` di.wang
2010-04-29  4:48   ` [Lustre-devel] Lustre RPC visualization Michael Kluge
     [not found]     ` <4BD9CF75.8030204@oracle.com>
2010-05-03  8:41       ` Michael Kluge
2010-05-03 13:20         ` Andreas Dilger
2010-05-03 18:10           ` Michael Kluge
2010-05-03 18:57             ` Robert Read
2010-05-03 18:58             ` di.wang
2010-05-03 19:32               ` Michael Kluge
2010-05-03 19:52                 ` di.wang
2010-05-03 20:04                   ` Michael Kluge
2010-05-16  9:29                   ` Michael Kluge
2010-05-16 13:12                     ` Eric Barton
2010-05-17  4:52                       ` Michael Kluge
2010-05-17  3:24                     ` Andrew Uselton
2010-05-17  5:53                       ` Michael Kluge
     [not found]                     ` <009101caf4f9$67e1dd50$37a597f0$%barton@oracle.com>
2010-05-17  3:39                       ` Shipman, Galen M.
2010-05-17  5:59                         ` Michael Kluge
2010-05-25 12:03                     ` Michael Kluge
     [not found]                       ` <4BFC7177.9000808@oracle.com>
2010-05-28 14:54                         ` Michael Kluge
     [not found]                           ` <4BFFA456.7030502@oracle.com>
     [not found]                             ` <C671351E-110C-4D2C-B216-4E8BE23A943A@oracle.com>
     [not found]                               ` <1FF3D25F-3369-462E-9651-62D56319612A@tu-dresden.de>
     [not found]                                 ` <D29ED098-3DEB-4AF4-AA68-B52B4E2BF5EA@oracle.com>
     [not found]                                   ` <4C04F3F0.9040708@oracle.com>
     [not found]                                     ` <001601cb01a3$546c93d0$fd45bb70$%barton@oracle.com>
2010-06-01 12:12                                       ` di.wang
2010-06-01 17:03                                         ` Andreas Dilger
2010-06-01 19:39                                           ` Michael Kluge
2010-06-16  8:46                                             ` Michael Kluge
2010-06-16 14:50                                               ` Andreas Dilger
2010-06-17 14:02                                                 ` Michael Kluge
     [not found]                                                   ` <4169315E-9A94-4430-8970-92068222EF15@oracle.com>
2010-06-20 20:44                                                     ` Michael Kluge
2010-06-22 15:12                                                       ` Michael Kluge
2010-06-23 10:29                                                         ` Alexey Lyashkov
2010-06-23 11:50                                                           ` Michael Kluge
2010-06-23 12:09                                                             ` Alexey Lyashkov
2010-06-23 12:38                                                               ` Michael Kluge
2010-06-23 15:55                                                             ` Andreas Dilger
2010-06-24  8:01                                                               ` Michael Kluge [this message]
2010-06-01 15:58                                     ` Eric Barton
2010-09-22 13:46                               ` Michael Kluge
2010-09-22 18:28                                 ` Andreas Dilger

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=44E9F0A8-5850-4FAA-992C-2C57D4F54AEE@tu-dresden.de \
    --to=michael.kluge@tu-dresden.de \
    --cc=lustre-devel@lists.lustre.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.