From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miroslav Lichvar Subject: Re: [RFC PATCH 6/7] net: allow simultaneous SW and HW transmit timestamping Date: Thu, 13 Apr 2017 16:59:44 +0200 Message-ID: <20170413145944.GB7490@localhost> References: <20170412141737.5881-1-mlichvar@redhat.com> <20170412141737.5881-7-mlichvar@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Network Development , Richard Cochran , Willem de Bruijn , Soheil Hassas Yeganeh , "Keller, Jacob E" , Denny Page , Jiri Benc To: Willem de Bruijn Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43359 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754480AbdDMO7r (ORCPT ); Thu, 13 Apr 2017 10:59:47 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Apr 13, 2017 at 10:30:32AM -0400, Willem de Bruijn wrote: > On Wed, Apr 12, 2017 at 10:17 AM, Miroslav Lichvar wrote: > > +SOF_TIMESTAMPING_OPT_MULTIMSG: > > + > > + Allow outgoing packets to be looped multiple times to the socket's > > + error queue in order to receive both software and hardware transmit > > + timestamps. > > + > > It is already possible to receive multiple copies of the same message. > Timestamps of type SCM_TSTAMP_SCHED will be passed for every > device, virtual or physical, such as bonding. With TCP retransmits, > multiple SCM_TSTAMP_SND can be observed. Oh, I see. I was struggling to find a good name for this option. > The name for this option is therefore not very descriptive. Perhaps > SOF_TIMESTAMPING_OPT_BOTH_SW_HW. Simultaneous SW/HW timestamping was already possible for incoming packets. Maybe _OPT_TX_SWHW would be better? -- Miroslav Lichvar