From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Accurate timestamps in received packets
Date: Mon, 12 Oct 2015 08:35:06 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20237E68D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <0dfde10b3f384fdb82358031522649b7@bilemail1.empirix.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Montorsi, Francesco
> Sent: Monday, October 12, 2015 9:26 AM
> To: Lu, Wenzhuo; dev@dpdk.org
> Subject: Re: [dpdk-dev] Accurate timestamps in received packets
>
> Hi Wenzhuo,
>
> > -----Original Message-----
> > From: Lu, Wenzhuo [mailto:wenzhuo.lu@intel.com]
> >
> > Why not
> > searching ieee1588 in the dpdk git repository? Surely you'll find
> > something.
>
> I tried using IEEE 1588 without success. In particular I enabled it at
> build-time of DPDK and then after calling rte_eth_rx_burst() I tried
> calling rte_eth_timesync_read_tx_timestamp() to get a timestamp from the
> port_id used to receive a burst of packets, but the function always
> returns with an error.
> Moreover, even if the function succeeded I need a timestamp for every
> incoming packet, not a single timestamp for the whole burst of received
> packets... do you know how I could achieve that?
Hi,
IEEE1588 isn't suitable for this. It is a timesync protocol rather than a timestamping function.
AFAIK, timestamping of every packet isn't supported by ixgbe/i40e nics and I don't know about non-Intel nics. It was supported for some(?) igb nics and hence the patch you linked to. Also, there isn't any DPDK API to enable/disable it even if it is supported by the nic.
John
next prev parent reply other threads:[~2015-10-12 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 15:30 Montorsi, Francesco
2015-10-10 4:52 ` Lu, Wenzhuo
2015-10-12 8:26 ` Montorsi, Francesco
2015-10-12 8:35 ` Mcnamara, John [this message]
2015-10-12 12:25 ` Montorsi, Francesco
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=B27915DBBA3421428155699D51E4CFE20237E68D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.com \
--cc=wenzhuo.lu@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).