From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Binna <stefan.binna@salzburgresearch.at>
Subject: Re: ieee1588fwd.c implementation
Date: Mon, 17 Aug 2015 10:47:40 +0200
Message-ID: <55D19FAC.20609@salzburgresearch.at>
References: <55CB6DC8.4090607@salzburgresearch.at>
 <B27915DBBA3421428155699D51E4CFE2022E480E@IRSMSX103.ger.corp.intel.com>
 <55CB7745.6040808@salzburgresearch.at>
 <B27915DBBA3421428155699D51E4CFE2022E488C@IRSMSX103.ger.corp.intel.com>
 <55CB833A.8090901@salzburgresearch.at> <55CC7F04.5040300@salzburgresearch.at>
 <B27915DBBA3421428155699D51E4CFE2022E6CEF@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
To: "Mcnamara, John" <john.mcnamara@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mx0.salzburgresearch.at (mx0.salzburgresearch.at
 [78.104.175.164]) by dpdk.org (Postfix) with ESMTP id 10DDC8D92
 for <dev@dpdk.org>; Mon, 17 Aug 2015 10:47:43 +0200 (CEST)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2022E6CEF@IRSMSX103.ger.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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?

Thanks. Best regards,
Stefan.

Am 14.08.2015 um 18:04 schrieb Mcnamara, John:
>> -----Original Message-----
>> From: Stefan Binna [mailto:stefan.binna@salzburgresearch.at]
>> Sent: Thursday, August 13, 2015 12:27 PM
>> To: Mcnamara, John; dev@dpdk.org
>> Subject: Re: [dpdk-dev] ieee1588fwd.c implementation
>>
>> I got PTP working and was able to transmit a valid PTPv2 packet over the
>> DPDK network card.
>>
>> Every time a PTP packet arrives I get following message in the testpmd
>> application: Port 0 Received PTP packet not filtered by hardware
>
> Hi,
>
> That may be due to 1 or 2 different issues:
>
>      1. You are using a NIC that doesn't support PTP timesyncing. What NIC are you using?
>      2. You are using a Fortville NIC but don't have the latest code from dpdk.org.
>
>
>> However, the hardware does not change the timestamp, when I check the
>> received packet.
> You will need to address the above issue first, but just to be clear, the NIC doesn't update the timestamp in the PTP packet. It sets a flag to say that the packet is a L2 PTP packet and that the timestamp of its arrival is available for reading.
>
> John
>