From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f65.google.com ([209.85.160.65]:42335 "EHLO mail-pl0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752052AbeCUO7f (ORCPT ); Wed, 21 Mar 2018 10:59:35 -0400 Received: by mail-pl0-f65.google.com with SMTP id w15-v6so3264531plq.9 for ; Wed, 21 Mar 2018 07:59:35 -0700 (PDT) Date: Wed, 21 Mar 2018 07:59:30 -0700 From: Richard Cochran To: Thomas Gleixner Cc: Eric Dumazet , Jesus Sanchez-Palencia , netdev@vger.kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us, vinicius.gomes@intel.com, intel-wired-lan@lists.osuosl.org, anna-maria@linutronix.de, henrik@austad.us, john.stultz@linaro.org, levi.pearson@harman.com, edumazet@google.com, willemb@google.com, mlichvar@redhat.com Subject: Re: [RFC v3 net-next 08/18] net: SO_TXTIME: Add clockid and drop_if_late params Message-ID: <20180321145930.4hlmihghljpv2wrq@localhost> References: <20180307011230.24001-1-jesus.sanchez-palencia@intel.com> <20180307011230.24001-9-jesus.sanchez-palencia@intel.com> <1520391209.109662.33.camel@gmail.com> <20180307052410.m2yqmokrivjlwcjz@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Mar 21, 2018 at 01:58:51PM +0100, Thomas Gleixner wrote: > Errm. No. There is no way to support fd based clocks or one of the CPU > time/process time based clocks for this. Why not? If the we have HW offloading, then the transmit time had better be expressed in terms of the MAC's internal clock. Otherwise we would need to translate between a kernel clock and the MAC clock, but that is expensive (eg over PCIe) and silly (because in a typical use case the MAC will already be synchronized to the network time). Thanks, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Date: Wed, 21 Mar 2018 07:59:30 -0700 Subject: [Intel-wired-lan] [RFC v3 net-next 08/18] net: SO_TXTIME: Add clockid and drop_if_late params In-Reply-To: References: <20180307011230.24001-1-jesus.sanchez-palencia@intel.com> <20180307011230.24001-9-jesus.sanchez-palencia@intel.com> <1520391209.109662.33.camel@gmail.com> <20180307052410.m2yqmokrivjlwcjz@localhost> Message-ID: <20180321145930.4hlmihghljpv2wrq@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Wed, Mar 21, 2018 at 01:58:51PM +0100, Thomas Gleixner wrote: > Errm. No. There is no way to support fd based clocks or one of the CPU > time/process time based clocks for this. Why not? If the we have HW offloading, then the transmit time had better be expressed in terms of the MAC's internal clock. Otherwise we would need to translate between a kernel clock and the MAC clock, but that is expensive (eg over PCIe) and silly (because in a typical use case the MAC will already be synchronized to the network time). Thanks, Richard