From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "idos-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org"
<idos-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Troy Leedberg <troy-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Subject: Re: ib_read_lat question
Date: Thu, 21 Feb 2013 12:34:39 -0600 [thread overview]
Message-ID: <512668BF.4030908@opengridcomputing.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A823736F35235F-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 2/21/2013 12:27 PM, Hefty, Sean wrote:
>> ib_read_lat displays RTT latency, while the other lat programs display
>> RTT/2. Is this intended? Or is read_lat.c/print_report() missing a
>> divide-by-two?
> The tests should measure how long it takes the data to reach the destination. For writes/sends, that would be RTT/2. For reads, the destination is local, so you should want RTT.
Guess that makes sense.
--
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:[~2013-02-21 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 17:50 ib_read_lat question Steve Wise
[not found] ` <51265E60.1070609-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-02-21 18:27 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F35235F-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-02-21 18:34 ` Steve Wise [this message]
[not found] ` <512668BF.4030908-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2013-02-27 8:46 ` Ido Shamai
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=512668BF.4030908@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=idos-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=troy-ut6Up61K2wZBDgjK7y7TUQ@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 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.