From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 6700E532C for ; Wed, 14 Nov 2018 11:14:23 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2018 02:14:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,232,1539673200"; d="scan'208";a="86379180" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga008.fm.intel.com with ESMTP; 14 Nov 2018 02:14:21 -0800 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.131]) by IRSMSX107.ger.corp.intel.com ([169.254.10.79]) with mapi id 14.03.0415.000; Wed, 14 Nov 2018 10:14:20 +0000 From: "Kovacevic, Marko" To: "Pattan, Reshma" , "dev@dpdk.org" , "longtb5@viettel.com.vn" , "Mcnamara, John" CC: "Pattan, Reshma" Thread-Topic: [dpdk-dev] [PATCH] doc: update timestamp validity for latency measurement Thread-Index: AQHUW90x/S5ueL8hmkS2YgaKWrc4l6VPTZiQ Date: Wed, 14 Nov 2018 10:14:19 +0000 Message-ID: <6DC05C7C5F25994B81B3F2F214251F66020502EA@IRSMSX104.ger.corp.intel.com> References: <1538655839-32339-1-git-send-email-reshma.pattan@intel.com> In-Reply-To: <1538655839-32339-1-git-send-email-reshma.pattan@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZGU0NDI4NzUtODc5Ny00MDM3LTg5ZGUtMGFlYzhjZTYyMTZiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVXVcL3RwRFhwUlwvdnJ6KzN6UVwvVkVBaXZYMnJFOFRLQmVTSUUxMHl1SU1sTjRQcFlGckFyVUtrZ0lDdk9lMnVhYyJ9 x-ctpclassification: CTP_NT x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] doc: update timestamp validity for latency measurement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2018 10:14:23 -0000 > Updated the doc on how packets are marked to identify their timestamp as > valid and considered for latency measurement. >=20 > Suggested-by: Bao-Long Tran > Signed-off-by: Reshma Pattan > > +Timestamp and latency calculation > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +The Latency stats library marks the time in the timestamp field of the > +mbuf for the ingress packets and sets the ``PKT_RX_TIMESTAMP`` flag of > +``ol_flags`` for the mbuf to indicate the marked time as a valid one. > +At the egress, the mbufs with the flag set are considered having valid > +timestamp and are used for the latency calculation. Acked-by: Marko Kovacevic