From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 43A7F8E78 for ; Mon, 12 Oct 2015 10:35:09 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 12 Oct 2015 01:35:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,671,1437462000"; d="scan'208";a="808855099" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by fmsmga001.fm.intel.com with ESMTP; 12 Oct 2015 01:35:08 -0700 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX106.ger.corp.intel.com (163.33.3.31) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 12 Oct 2015 09:35:06 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.116]) by irsmsx112.ger.corp.intel.com ([169.254.1.218]) with mapi id 14.03.0248.002; Mon, 12 Oct 2015 09:35:06 +0100 From: "Mcnamara, John" To: "Montorsi, Francesco" , "Lu, Wenzhuo" , "dev@dpdk.org" Thread-Topic: Accurate timestamps in received packets Thread-Index: AdECoeRGBbnp2n4lTluzoJeGQ8/KtgAdUWggAGtJMGAAAPEEQA== Date: Mon, 12 Oct 2015 08:35:06 +0000 Message-ID: References: <825e846fd8934cc0b34293a8a1542bd2@bilemail1.empirix.com> <6A0DE07E22DDAD4C9103DF62FEBC09090209D3D5@shsmsx102.ccr.corp.intel.com> <0dfde10b3f384fdb82358031522649b7@bilemail1.empirix.com> In-Reply-To: <0dfde10b3f384fdb82358031522649b7@bilemail1.empirix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Accurate timestamps in received packets X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2015 08:35:09 -0000 > -----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 >=20 > Hi Wenzhuo, >=20 > > -----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 t= imestamping 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 an= d hence the patch you linked to. Also, there isn't any DPDK API to enable/d= isable it even if it is supported by the nic. John