From owner-freebsd-net@freebsd.org Tue Jun 2 11:53:56 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1FEC93334E4 for ; Tue, 2 Jun 2020 11:53:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49br6V4x4lz4c9k for ; Tue, 2 Jun 2020 11:53:54 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id 052Brhgt018789 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 2 Jun 2020 14:53:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 052Brhgt018789 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id 052BrhP9018788; Tue, 2 Jun 2020 14:53:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 2 Jun 2020 14:53:43 +0300 From: Konstantin Belousov To: Gabriel.Moyano@dlr.de Cc: freebsd-net@freebsd.org Subject: Re: HW timestamping e1000 Message-ID: <20200602115343.GO48478@kib.kiev.ua> References: <798afa552a794a0f9c07aa2fca422ea3@dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <798afa552a794a0f9c07aa2fca422ea3@dlr.de> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 49br6V4x4lz4c9k X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [1.65 / 15.00]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_SPAM_SHORT(0.56)[0.557]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; TO_DN_NONE(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_MEDIUM(0.44)[0.439]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.65)[0.651]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2020 11:53:56 -0000 On Tue, Jun 02, 2020 at 10:46:00AM +0000, Gabriel.Moyano@dlr.de wrote: > Hi everybody, > > Currently I am writing a piece of code to test HW timestamping on e1000 during reception, which runs on FreeBSD 12, but unfortunately it seems that it isn't working. > > The socket is created and configured as follows: > > sockfd = socket(AF_INET, SOCK_DGRAM, 0); > int on = 1; > setsockopt(sockfd, SOL_SOCKET, SO_TIMESTAMP, &on, sizeof(on)); > > After recvmsg() is called, cmsg_type of received control messages are printed out with help of the control message routines (https://www.freebsd.org/cgi/man.cgi?query=CMSG_DATA). SCM_TIME_INFO should be printed out but it's not. > > Is there any configuration missing? Does e1000 support HW timestamping right? > > I will appreciate any help. Hardware timestamping is only implemented for Mellanox ConnectX-4 and hier, and Chelsio Terminators (T4 and newer ?). It might be doable for Intel some cards, but not all of them.