DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kai Zhang <zhang.4522@osu.edu>
To: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>, alex@weka.io
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] About round trip latency with DPDK
Date: Fri, 25 Jul 2014 10:21:07 -0400	[thread overview]
Message-ID: <CACKSPmfwrUp0HyEt+hwqvPGtm_=+jcqh6zwh9o1qbwz7yVaq1w@mail.gmail.com> (raw)
In-Reply-To: <F6F2A6264E145F47A18AB6DF8E87425D12B0782C@IRSMSX102.ger.corp.intel.com>

Thanks!

I have found the problem. It is that I used clock_gettime() to measure the
latency. With rte_rdtsc(), the round trip latency is measured to be less
than 10 microseconds.

Thanks very much,
Kai


On Thu, Jul 24, 2014 at 8:48 AM, Wodkowski, PawelX <
pawelx.wodkowski@intel.com> wrote:

> Refer to DPDK getting started guide paragraph 5.4. It might help.
> Also it might be easier to do write simple application that send a packet
> on port 1 and rx it on port 2 in separate threads on separate cores (simple
> physical loop). You can then add timestamp and send packet back and see how
> long it will take TX to RX and RX to TX process.
>
> Pawel Wodkowski
> --------------------------------------------------------------
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> Business address: Dromore House, East Park, Shannon, Co. Clare
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
>

  reply	other threads:[~2014-07-25 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:48 Wodkowski, PawelX
2014-07-25 14:21 ` Kai Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-23 19:24 Kai Zhang
2014-07-24  8:36 ` Alex Markuze

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='CACKSPmfwrUp0HyEt+hwqvPGtm_=+jcqh6zwh9o1qbwz7yVaq1w@mail.gmail.com' \
    --to=zhang.4522@osu.edu \
    --cc=alex@weka.io \
    --cc=dev@dpdk.org \
    --cc=pawelx.wodkowski@intel.com \
    /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).