From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AE363A2E8C for ; Thu, 5 Sep 2019 16:23:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7F3B91EFB1; Thu, 5 Sep 2019 16:23:18 +0200 (CEST) Received: from mail.deltatec.be (mxbackup1.deltatec.be [62.197.119.12]) by dpdk.org (Postfix) with ESMTP id 73E1E1EFB0 for ; Thu, 5 Sep 2019 16:23:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deltatec.be; s=AnsUTM; h=MIME-Version:Content-Type:Message-ID:Date:Subject:To:From; bh=5Q2zNp8yHAACzBWi0DPjdcLwBsq0pXKAMvOSXKZO9PE=; b=PbcqmcoWsyV4wYhS/ZLIs8cHZZUsFbhbBTPRBQsF2r2hW9lEsFWsAf2kzLDpombE7jHHq4p3IkypINkGtkLn8mR/6Rp+6KPWc2fsatW4EQoiAA3Q6aW3zXeXptgXPLHhvbTnQe1BIpkJg6jzjI8i+RzO4WK/03//HTdiZNRVNDg=; Received: from [172.16.4.5] (port=55126 helo=W2K16-SVR-5.office.deltatec.net) by mail.deltatec.be with esmtps (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1i5sfJ-00068K-2e for users@dpdk.org; Thu, 05 Sep 2019 16:23:14 +0200 Received: from W2K16-SVR-5.office.deltatec.net (172.16.4.5) by W2K16-SVR-5.office.deltatec.net (172.16.4.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1034.26; Thu, 5 Sep 2019 16:23:13 +0200 Received: from W2K16-SVR-5.office.deltatec.net ([::1]) by W2K16-SVR-5.office.deltatec.net ([::1]) with mapi id 15.01.1034.026; Thu, 5 Sep 2019 16:23:13 +0200 X-CTCH-RefID: str=0001.0A090214.5D711A51.0085, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 From: Philippe CORNET To: "users@dpdk.org" Thread-Topic: PTP client over DPDK Thread-Index: AdVj9RbG9R6E4JgXSQ6ps4Qg+EmE3A== Date: Thu, 5 Sep 2019 14:23:13 +0000 Message-ID: <399f94faf87f41f59a9786aa245e94b0@deltatec.be> Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.6.82] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] PTP client over DPDK X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi all, I am currently wondering what is the best/cheapest way to implement a PTP c= lient over DPDK: 1. Implementing a custom PTP client over DPDK. or 2. Using LinuxPTP (http://linuxptp.sourceforge.net/) through KNI inte= rface. 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 re= quires these modifications: - To build KNI with flag CONFIG_RTE_KNI_PREEMPT_DEFAULT=3Dn to red= uce latency of KNI - To patch kni_net.c to add a software timestamping of the skb (sk= b_tx_timestamp(skb)) in tx routine. - To patch LinuxPTP to avoid it checking the software-transmit tim= e stamping capability of the KNI driver. Solution 2 is tempting because it almost costs nothing in term of developme= nt 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