From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zr@semihalf.com>
Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com
 [209.85.215.195]) by dpdk.org (Postfix) with ESMTP id B0A3B1B12D
 for <dev@dpdk.org>; Wed,  5 Dec 2018 17:33:37 +0100 (CET)
Received: by mail-pg1-f195.google.com with SMTP id w7so9243243pgp.13
 for <dev@dpdk.org>; Wed, 05 Dec 2018 08:33:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=semihalf-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:in-reply-to:references;
 bh=3ggqkUl+3rf98MmttuPqyLdOCmJ2Fb4L5vAJBjKzlHA=;
 b=IA0Bp6Naa2U5NtemhjZlcZGIV7UsxHn2jVzw/n5vXtj5i/HzHvQgy3MddiNLulZZ1D
 /KQRnJSxwzex6M99hoLADSdj35a24CY7ol7tc7RCYbNkBmHp+F+DvXa5lDS/wbSV8Nvi
 RevYafZqg5hS8cV7Vcy81oAqlTjLJNWfanGCER3D0Bp5KVZlyy3cdh34rlvoNN0MbPS5
 OUmlA1vLeFPoghT0AJ3wMdq7IbCM+j/YnCfSEXlwzu7qdky5Ohy4pvwEkgT2RPzJqUDM
 kf+k922rBh/7eQDKRmQrjAEFn+wXeD3h3sfpp9IxhuuHB+GsRPX+COuugZ9bCnjHekdS
 EdcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to
 :references;
 bh=3ggqkUl+3rf98MmttuPqyLdOCmJ2Fb4L5vAJBjKzlHA=;
 b=luzpJgx6uyNbr5qr7i0zIZO2rk/377+Ar/do3Po9/Fxrva8BITsDL5M/8WLvKqGqEg
 GupPCtw8z1TKhFbWGSnHe16EL1p8RZT0r8aB6+BHLIIfFpLUnvfboQbKn18gI+/QKcnJ
 qirpBUTeQjSoe1HUaq5IcQGkmw3KAVJON711HNPse7Y1g4DIX8U9EeKZG8lZ79qXkUQw
 QEvmGowehHhZ6lWOUViW0pa91GbTgE6UIQBw3oRZznNjW904tmS/z7azCPv575tT2mn5
 JFiA/R+DQJvwGnSQAZ8Rfz7rjGraPofX4HTfZbRKUpv86heZLSulc1iwkpVjDAvS3EJq
 qHag==
X-Gm-Message-State: AA+aEWYNpNsu9gDraWqvuNSJYc1GHM6b1itnK3jGi/z5l+NzM+u1jHoD
 JwVk/pd8043189Y+3+E2WlFpD3XU023P+A==
X-Google-Smtp-Source: AFSGD/VuCh8417HsP5K156wubBxMvXgTLuUiqP80MMIrC67MUdsKrlc47ktXdAOEZRVKbQrfbK9snA==
X-Received: by 2002:a62:6799:: with SMTP id t25mr24950026pfj.139.1544027616827; 
 Wed, 05 Dec 2018 08:33:36 -0800 (PST)
Received: from localhost.localdomain
 (50-193-63-94-static.hfc.comcastbusiness.net. [50.193.63.94])
 by smtp.gmail.com with ESMTPSA id n73sm30719048pfj.148.2018.12.05.08.33.34
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Wed, 05 Dec 2018 08:33:35 -0800 (PST)
From: zr@semihalf.com
To: barbette@kth.se,
	dev@dpdk.org
Cc: Zyta Szpak <zr@semihalf.com>
Date: Wed,  5 Dec 2018 17:33:20 +0100
Message-Id: <1544027600-9390-1-git-send-email-zr@semihalf.com>
X-Mailer: git-send-email 2.7.4
In-Reply-To: <1543398732-79439-2-git-send-email-barbette@kth.se>
References: <1543398732-79439-2-git-send-email-barbette@kth.se>
Subject: Re: [dpdk-dev] [RFC PATCH 0/3] Add rte_eth_read_clock API
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 16:33:37 -0000

From: Zyta Szpak <zr@semihalf.com>

I'd ask few questions: how is this new rte_ethdev_read_clock different from existing rte_eth_timesync_read_time ?
Is it that this new function does not convert the clock raw value into timespec? Would it be too much overhead to use the timespec type of value? Or do they intent to read different clocks?