From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] eal: roundup tsc frequency when estimating it Date: Thu, 29 Nov 2018 13:21:52 -0800 Message-ID: <20181129132152.754ce410@xeon-e3> References: <20181129083138.23029-1-pbhagavatula@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Jacob, Jerin" , "dev@dpdk.org" , "Bhagavatula, Pavan" To: Pavan Nikhilesh Return-path: Received: from mail-pl1-f193.google.com (mail-pl1-f193.google.com [209.85.214.193]) by dpdk.org (Postfix) with ESMTP id 69EB61B4DC for ; Thu, 29 Nov 2018 22:22:01 +0100 (CET) Received: by mail-pl1-f193.google.com with SMTP id b5so1670579plr.4 for ; Thu, 29 Nov 2018 13:22:01 -0800 (PST) In-Reply-To: <20181129083138.23029-1-pbhagavatula@caviumnetworks.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" On Thu, 29 Nov 2018 08:32:03 +0000 Pavan Nikhilesh wrote: > When estimating tsc frequency using sleep/gettime round it up to the > nearest multiple of 10Mhz for more accuracy. > > Signed-off-by: Pavan Nikhilesh Rounding reduces accuracy. Why is this code being used? Shouldn't get_tsc_freq_arch return a correct value? How well does the rdmsr() logic work in VM? It looks like Hyper-V has special MSR's for TSC frequency determination.