From: Phillip Susi <psusi@ubuntu.com>
To: linux-btrace@vger.kernel.org
Subject: Re: Events out of order
Date: Wed, 31 Dec 2014 03:23:28 +0000 [thread overview]
Message-ID: <54A36C30.8010105@ubuntu.com> (raw)
In-Reply-To: <54A355D2.5060704@ubuntu.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/30/2014 08:53 PM, Alireza Haghdoost wrote:
> Can you please share an example ? How much time backward you
> observed after switch ?
8,64 2 606 0.019550771 480 D R 2816 + 128 [kworker/2:1H]
8,64 2 607 0.019551057 480 R R 2816 + 128 [0]
8,64 2 608 0.019551151 480 I R 2816 + 128 [kworker/2:1H]
8,64 2 609 0.019979263 0 D R 2816 + 128 [swapper/2]
8,64 2 610 0.019980728 0 D R 2944 + 128 [swapper/2]
8,64 2 611 0.020403185 0 C R 2816 + 128 [0]
8,64 2 612 0.020416690 0 R R 2944 + 128 [0]
8,64 2 613 0.020416798 0 I R 2944 + 128 [swapper/2]
8,64 2 614 0.020420237 480 D R 2944 + 128 [kworker/2:1H]
8,64 2 615 0.020420511 480 R R 2944 + 128 [0]
8,80 2 2 0.000000042 27566 G R 0 + 8 [hdparm]
8,80 2 3 0.000001130 27566 P N [hdparm]
8,80 2 4 0.000003388 27566 Q R 8 + 8 [hdparm]
8,80 2 5 0.000004343 27566 M R 8 + 8 [hdparm]
8,80 2 6 0.000005793 27566 Q R 16 + 8 [hdparm]
8,80 2 7 0.000005979 27566 M R 16 + 8 [hdparm]
8,80 2 8 0.000006934 27566 Q R 24 + 8 [hdparm]
8,80 2 9 0.000007092 27566 M R 24 + 8 [hdparm]
Come to think of it, in this example it didn't even switch to the
other cpu, just the other device ( though typically when that happens
it seems to also switch the cpu ).
Here is one that is worse:
8,64 1 1026 0.075645831 27565 Q R 7800 + 8 [hdparm]
8,64 1 1027 0.075646030 27565 M R 7800 + 8 [hdparm]
8,64 1 1028 0.075646911 27565 Q R 7808 + 8 [hdparm]
8,64 1 1029 0.075647447 27565 G R 7808 + 8 [hdparm]
8,80 0 1 0.035128312 27566 Q R 5376 + 8 [hdparm]
8,80 0 2 0.035130922 27566 G R 5376 + 8 [hdparm]
8,80 0 3 0.035131724 27566 P N [hdparm]
Would you like the raw trace file?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJUo2wwAAoJENRVrw2cjl5RIooH/juX4p9Cz9XLjYbpLL0HtZhb
JnGw4yaZQEBeqBs5h1LL3A6JZnNHx/yAxMO6LteWr4aQf+nKWUyLD+Yj0jid3n+u
MF4yAwYI7PtJZtRzYpY0YlCorQdX2GKj1ajcX4mCHXrmMr2AXr4Ionyek042Q/Lp
cpJRJUL7OfHHhtpTRTf5Xg36yLo/nK1cIFU0bNz21U3o7jWKRKo7PAmulZymCdN0
4FULblVSqiC3iqWPFQC8ScYLxZa0uKnsA73hFB4NbVXVXOoDor2DbgiQoF8gKVWn
MmYlMwf5wfBwuPDTaTcVVLNA7weK6Gs79T71/6FLiJGnpaeedDAQyKvYx3j+5PQ=nd6f
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-31 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 1:48 Events out of order Phillip Susi
2014-12-31 1:51 ` Phillip Susi
2014-12-31 1:53 ` Alireza Haghdoost
2014-12-31 3:23 ` Phillip Susi [this message]
2014-12-31 4:29 ` Alireza Haghdoost
2014-12-31 14:36 ` Phillip Susi
2014-12-31 14:58 ` Chris Mason
2014-12-31 15:09 ` Phillip Susi
2014-12-31 15:19 ` Jens Axboe
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=54A36C30.8010105@ubuntu.com \
--to=psusi@ubuntu.com \
--cc=linux-btrace@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).