From: Michael Kluge <Michael.Kluge@tu-dresden.de>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre RPC visualization
Date: Mon, 03 May 2010 22:04:11 +0200 [thread overview]
Message-ID: <4BDF2C3B.8050505@tu-dresden.de> (raw)
In-Reply-To: <4BDF2999.2000207@oracle.com>
OK, sounds reasonable. I can put the number of ignored messages in an
additional counter. That should make the generated trace file more
descriptive.
Regards, Michael
Am 03.05.2010 21:52, schrieb di.wang:
>> Anyway, what can get lost? Any kind of
>> message on the servers and clients? I think I'd like to know what
>> cases have to be handled while I try to track individual RPC's on
>> their way.
> Any records can get lost here. Unfortunately, there are not any messages
> indicate the missing happened. :(
> (Usually, I would check the time stamp in the log, i.e. no records for a
> "long" time, for example several seconds, but this is not the accurate
> way).
>
> I guess you can just ignore these uncompleted records in your first
> step? Let's see how these incomplete log will
> impact the profiling result, then we will decide how to deal with this?
>
next prev parent reply other threads:[~2010-05-03 20:04 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 [this message]
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
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=4BDF2C3B.8050505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox