DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stefan Binna <stefan.binna@salzburgresearch.at>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] ieee1588fwd.c implementation
Date: Thu, 13 Aug 2015 13:27:00 +0200	[thread overview]
Message-ID: <55CC7F04.5040300@salzburgresearch.at> (raw)
In-Reply-To: <55CB833A.8090901@salzburgresearch.at>

Hi John,

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

However, the hardware does not change the timestamp, when I check the 
received packet.

How can I enable this feature?

Thanks very much.
Kind regards, Stefan.

Am 12.08.2015 um 19:32 schrieb Stefan Binna:
> Hi John,
>
> thanks very much for the big help :)
>
> I'll try it tomorrow and if I run into any problems I'll contact you 
> again.
>
> Best regards,
> Stefan.
>
> Am 12.08.2015 um 19:09 schrieb Mcnamara, John:
>>> -----Original Message-----
>>> From: Stefan Binna [mailto:stefan.binna@salzburgresearch.at]
>>> Sent: Wednesday, August 12, 2015 5:42 PM
>>> To: Mcnamara, John; dev@dpdk.org
>>> Subject: Re: [dpdk-dev] ieee1588fwd.c implementation
>>>
>>> Hi John,
>>>
>>>
>>> I don't understand how to implement ieee1588fwd. Is there any manual,
>>> sample application or similar available?
>>> Or do I have to modify the testpmd.c file by myself? I don't really 
>>> know
>>> how to implement the code available in ieee1588fwd.c.
>> Hi Stefan,
>>
>> The steps you did are correct:
>>
>>      * Enable CONFIG_RTE_LIBRTE_IEEE1588=y in the config.
>>      * Compile the testpmd application (this happens as part of the 
>> default compile):
>>
>>            make -j T=x86_64-native-linuxapp-gcc install
>>
>> Then you can run testpmd with ieee1588 forwarding on as follows (or 
>> similar. Adjust coremask to suit):
>>
>>      sudo ./x86_64-native-linuxapp-gcc/app/testpmd -c 300 -n 4 \
>>            --  --port-topology=chained --txqflags=0 
>> --forward-mode=ieee1588
>>
>> Note:
>>      The --txqflags=0 is required to ensure ieee1588 support in the 
>> "full featured" TX path.
>>
>> If you send the correct l2 ptp packets they should generate a text 
>> output from testpmd
>>
>> Add '-i' after '--' to enter interactive mode in testpmd.
>>
>> You can also set IEEE1588 mode from within testpmd as follows:
>>
>>      testpmd> set fwd ieee1588
>>      Set ieee1588 packet forwarding mode
>>
>>
>> Note: if you don't see the ieee1588 mode it usually means that 
>> CONFIG_RTE_LIBRTE_IEEE1588 wasn't configured.
>>
>> Best of luck,
>>
>> John.
>

  reply	other threads:[~2015-08-13 11:27 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 [this message]
2015-08-14 16:04           ` Mcnamara, John
2015-08-17  8:47             ` Stefan Binna
2015-08-17 14:21               ` Mcnamara, John
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=55CC7F04.5040300@salzburgresearch.at \
    --to=stefan.binna@salzburgresearch.at \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).