From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
 [209.85.212.170]) by dpdk.org (Postfix) with ESMTP id 98AE3B373
 for <dev@dpdk.org>; Thu, 28 Aug 2014 11:02:05 +0200 (CEST)
Received: by mail-wi0-f170.google.com with SMTP id cc10so200505wib.5
 for <dev@dpdk.org>; Thu, 28 Aug 2014 02:06:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=bulFtyquERGk51fqfHhQkehPsheU/79cQuq3L1q9Xgs=;
 b=aCfq4O47jQJiCV64oH6EJVaiJH2EGNhvQWH5Bk1gtHdl7Ye7yPiv/zsDqALVa/S22L
 xuXu44xOMVzsd8ZvrU1jeBfQji+i1qcB4ZvWGV247BXhGsUsQV+qnZNoqDiVaWlMapjD
 aWUSvM7SIUNGGN5LFItinKXUSJJbVsXOJUcXRlbs4SBh4ON2BDvdrV5rgK654JufRf/L
 5eM84zQYsQeu4N3KBgMTTcjmXUxnnPiqu+8b5KX7LNvu+vbj1ZRjLiY1SWwDq4Al95uz
 WDN1W/aCjXUS1kaKGiHlBZZqGiyQ8SAeJn+1mpUdfdNlmxXpa0/8cySnfwT4LxefZd7b
 xX5w==
X-Gm-Message-State: ALoCoQnjepovfmLOA3GM7+tMkFRd1UcarZrJRYqddQeR4L/b9mbxbSRS2UPlR4wDzBdBPjv8fChq
X-Received: by 10.180.19.10 with SMTP id a10mr10372871wie.49.1409216773671;
 Thu, 28 Aug 2014 02:06:13 -0700 (PDT)
Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net.
 [82.239.227.177])
 by mx.google.com with ESMTPSA id z8sm33291211wiv.24.2014.08.28.02.06.12
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 28 Aug 2014 02:06:12 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Date: Thu, 28 Aug 2014 11:06:07 +0200
Message-ID: <2353283.PtiVvKdYNr@xps13>
Organization: 6WIND
User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; )
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0343ECAF0@IRSMSX103.ger.corp.intel.com>
References: <1598074.SMl35i2x6y@xps13> <53FE0FA5.8020900@tilera.com>
 <59AF69C657FD0841A61C55336867B5B0343ECAF0@IRSMSX103.ger.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] next releases
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 09:02:05 -0000

2014-08-28 08:41, Richardson, Bruce:
> As for rte_rdtsc_precise, I'm not sure about its origins, but I'm
> surprised to see that it does not correspond to the rdtscp instruction.
> Can anyone else comment on this one? I would assume it's designed
> to be used to get more accurate measurements of smaller blocks of
> code that we want to benchmark, since rdtsc works best when timing
> larger blocks (in terms of cycle counts, that is, not source lines :-) ).

The good thing with git history (and well written commit logs) is that
we can easily get such answer:
	http://dpdk.org/browse/dpdk/commit/?id=3314648f83c3dc06d7d9a

Bruce, do you know how rdtscp is supported across Intel processors?

-- 
Thomas