DPDK usage discussions
 help / color / Atom feed
* Re: [dpdk-users] PTP client over DPDK
@ 2019-11-07  8:38 Marcin Kulawczuk
  0 siblings, 0 replies; 2+ messages in thread
From: Marcin Kulawczuk @ 2019-11-07  8:38 UTC (permalink / raw)
  To: p.cornet; +Cc: users

Hi,

We are struggling with same problem as you (working on PTP implementation
in dpdk), so I've got a question to you, would you recommend solution 2 for
us or have you found some problems with it?

Thanks,
Marcin

-- 


-------------------------------
The information in this email is 
confidential and may be legally privileged, it may contain information that 
is confidential in CodiLime Sp. z o. o. It is intended solely for the 
addressee. Any access to this email by third parties is unauthorized. If 
you are not the intended recipient of this message, any disclosure, 
copying, distribution or any action undertaken or neglected in reliance 
thereon is prohibited and may result in your liability for damages.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [dpdk-users] PTP client over DPDK
@ 2019-09-05 14:23 Philippe CORNET
  0 siblings, 0 replies; 2+ messages in thread
From: Philippe CORNET @ 2019-09-05 14:23 UTC (permalink / raw)
  To: users

Hi all,

I am currently wondering what is the best/cheapest way to implement a PTP client over DPDK:


1.       Implementing a custom PTP client over DPDK.
or

2.       Using LinuxPTP (http://linuxptp.sourceforge.net/) through KNI interface.

For solution 1, we can start from the PTP sample program, but it certainly requires quite some time to develop a smart and accurate client.

For solution 2, I have a proof-of-concept which works quite well, but it requires these modifications:

-          To build KNI with flag CONFIG_RTE_KNI_PREEMPT_DEFAULT=n to reduce latency of KNI

-          To patch kni_net.c to add a software timestamping of the skb (skb_tx_timestamp(skb)) in tx routine.

-          To patch LinuxPTP to avoid it checking the software-transmit time stamping capability of the KNI driver.

Solution 2 is tempting because it almost costs nothing in term of development time, but I am not sure that it is the good way to proceed...

Does anyone has strong arguments for or against this second solution?

Thanks,
Philippe



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-07  8:38 [dpdk-users] PTP client over DPDK Marcin Kulawczuk
  -- strict thread matches above, loose matches on Subject: below --
2019-09-05 14:23 Philippe CORNET

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox