From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Stefan Binna <stefan.binna@salzburgresearch.at>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ieee1588fwd.c implementation
Date: Mon, 17 Aug 2015 14:21:31 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2022E787B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <55D19FAC.20609@salzburgresearch.at>
> -----Original Message-----
> From: Stefan Binna [mailto:stefan.binna@salzburgresearch.at]
> Sent: Monday, August 17, 2015 1:48 AM
> To: Mcnamara, John; dev@dpdk.org
> Subject: Re: [dpdk-dev] ieee1588fwd.c implementation
>
> Hi,
>
> I'm using the Intel NIC 82547L.
> Furthermore I'm using DPDK-2.0.0, the last stable download from the
> official homepage.
>
> Is there any method to "measure" the time the NIC takes to process the
> packet from the input port (e.g. port 0) to the output port (port 1)?
> Should be around 8 to 40 microseconds depending on the packet size?
Hi Stefan,
The RX/TX callbacks sample application looks closer to what you are looking for:
"The RX/TX Callbacks sample application is a packet forwarding application
that demonstrates the use of user defined callbacks on received and transmitted
packets. The application performs a simple latency check, using callbacks,
to determine the time packets spend within the application".
http://dpdk.org/doc/guides/sample_app_ug/rxtx_callbacks.html
http://dpdk.org/browse/dpdk/tree/examples/rxtx_callbacks/main.c
John.
--
next prev parent reply other threads:[~2015-08-17 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 16:01 Stefan Binna
2015-08-12 16:24 ` Mcnamara, John
2015-08-12 16:41 ` Stefan Binna
2015-08-12 17:09 ` Mcnamara, John
2015-08-12 17:32 ` Stefan Binna
2015-08-13 11:27 ` Stefan Binna
2015-08-14 16:04 ` Mcnamara, John
2015-08-17 8:47 ` Stefan Binna
2015-08-17 14:21 ` Mcnamara, John [this message]
2015-08-18 7:38 ` Stefan Binna
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=B27915DBBA3421428155699D51E4CFE2022E787B@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=stefan.binna@salzburgresearch.at \
/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).