From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 2/3] app/testpmd: enabled control for packet timestamps Date: Tue, 25 Apr 2017 18:22:17 +0200 Message-ID: <5493210.cW0TSkhqM8@xps> References: <1476369308-17021-1-git-send-email-olegk@mellanox.com> <1476369308-17021-3-git-send-email-olegk@mellanox.com> <9BB6961774997848B5B42BEC655768F810D4D536@SHSMSX103.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Oleg Kuporosov , olivier.matz@6wind.com To: "Wu, Jingjing" Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 258BF559A for ; Tue, 25 Apr 2017 18:22:19 +0200 (CEST) In-Reply-To: <9BB6961774997848B5B42BEC655768F810D4D536@SHSMSX103.ccr.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, 25/04/2017 16:02, Wu, Jingjing: > From: Oleg Kuporosov > > Implemented two methods of control > > > > - by --enable-timestamps CL testpmd application we can enable timestamping > > for all ports; > > - in interactive mode port config timestamps on|off is able to > > configure timestamping per specific port. > > > > The control doesn't interact with IEEE1588 PTP implementation there as it is > > under macro compilation but can be extended in the future. > > > > This feature is required for debugging/testing purposes for real time HW packet > > timestamping. > > We have ieee1588fwd.c to demo the timesync enable/disable, can we reuse > The fwd engine instead of defining new commands? Yes for IEEE1588 feature, we should use app/test-pmd/ieee1588fwd.c. There is more to say about this feature. The main goal of this patchset was to add a timestamp in the mbuf. It has been done by another patchset in 17.05. Do we know how to test this timestamp in testpmd? About IEEE1588 feature, why is there a config option? CONFIG_RTE_LIBRTE_IEEE1588 A feature should never be disabled at compile time. There is also a runtime enablement with rte_eth_timesync_enable(). I think we need some discussions here. Thanks