From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dlrmsghd@gmail.com>
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com
 [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id 5F042FFA
 for <dev@dpdk.org>; Mon,  1 Jun 2015 05:48:16 +0200 (CEST)
Received: by wicmx19 with SMTP id mx19so62995901wic.0
 for <dev@dpdk.org>; Sun, 31 May 2015 20:48:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=xxIPL2vMn//LcyzeTsZc1DnrmaXD5mlTOQpUREbx7Do=;
 b=yNVNgk/vPWFuGNnY7a2t+e2Uhn27AHRpm952/gKGJIyGZVmXDZFUN8GlKUxVhZeZSU
 Ta2Rxj6jzawRs3lb1z4KVeP1O1+mVzPA3+MCPwvXef6dcnvsBUJH2rD71qaYiAJIHoZx
 5UMebzWEHYcNjWEovv4peQcuL27HCs0hpbb9PYc5ioiUkFtUzJc4gNKHpAeuDiLKhN1c
 bbMQxoNy1QPoiZbT38n1+DQEU3Yo2HcRT/0GjTWoPf0/ivTQHBywAVNke7xKjDk7dGp1
 AVjuglHqYaINOB1IcAyRwicpQtp3ztVxc/taeuBRO+KHuRIZxWuKAZi8ryI8K6zsU+TE
 cm4g==
MIME-Version: 1.0
X-Received: by 10.194.103.2 with SMTP id fs2mr37446710wjb.151.1433130496214;
 Sun, 31 May 2015 20:48:16 -0700 (PDT)
Received: by 10.28.173.196 with HTTP; Sun, 31 May 2015 20:48:16 -0700 (PDT)
In-Reply-To: <002a01d09c14$16911430$43b33c90$@colasoft.com.cn>
References: <002a01d09c14$16911430$43b33c90$@colasoft.com.cn>
Date: Mon, 1 Jun 2015 12:48:16 +0900
Message-ID: <CAKBXKmCvwU3oF9dTLyApHhjLd3pSX6pUydW-CR3cFkCOECtXWA@mail.gmail.com>
From: Keunhong Lee <dlrmsghd@gmail.com>
To: =?UTF-8?B?56eR5p2lIOiwreaYpea1tw==?= <chunhai.tan@colasoft.com.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to set timestamp in 82599 NICs in DPDK?
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: Mon, 01 Jun 2015 03:48:16 -0000

82599 supports hw timestamping for PTP packets.
I don't know whether it supports timestamping for general packets.


http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgbe=
_ptp.c#L640
says that

640 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/=
ixgbe_ptp.c#L640>*
        default:
*641 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe=
/ixgbe_ptp.c#L641>*
                /**642
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgb=
e_ptp.c#L642>*
                 * register RXMTRL must be set in order to do V1
packets,*643 <http://lxr.free-electrons.com/source/drivers/net/ethernet/int=
el/ixgbe/ixgbe_ptp.c#L643>*
                 * therefore it is not possible to time stamp both V1
Sync and*644 <http://lxr.free-electrons.com/source/drivers/net/ethernet/int=
el/ixgbe/ixgbe_ptp.c#L644>
*                 * Delay_Req messages and hardware does not support**
645 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/=
ixgbe_ptp.c#L645>
                 * timestamping all packets =3D> return error
*646 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe=
/ixgbe_ptp.c#L646>*
                 */*647
<http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe/ixgb=
e_ptp.c#L647>
                config
<http://lxr.free-electrons.com/ident?i=3Dconfig>*->rx_filter =3D
HWTSTAMP_FILTER_NONE;
*648 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe=
/ixgbe_ptp.c#L648>*
                return -*ERANGE
<http://lxr.free-electrons.com/ident?i=3DERANGE>*;
*649 <http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/ixgbe=
/ixgbe_ptp.c#L649>*
        }*


Keunhong.

2015-06-01 11:38 GMT+09:00 =E7=A7=91=E6=9D=A5 =E8=B0=AD=E6=98=A5=E6=B5=B7 <=
chunhai.tan@colasoft.com.cn>:

> Hi
>
>
>
> I noticed that there is a patch which can set hardware timestamp for the
> received
> packets(
> http://www.wand.net.nz/trac/libtrace/browser/Intel%20DPDK%20Patches/
> hardware_timestamp.patch?rev=3Dce7153dbc6a13c18bf8033af08c1249527754168),
> but
> it only works in e1000 and igb NICs. I want to capture packets with
> timestamp info in 82599 NICs, what should I do? Could you give me some
> help?
>
>
>
> Thanks.
>
>
>
> Chunhai Tan
>
>
>
>
>
>