Received-SPF: pass (google.com: domain of linux-kernel+bounces-18147-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Precedence: bulk
MIME-Version: 1.0
References: <20240104212439.3276458-1-maheshb@google.com> <ZZczNlXzM8lrZgH5@hoboy.vegasvil.org>
In-Reply-To: <ZZczNlXzM8lrZgH5@hoboy.vegasvil.org>
From: =?UTF-8?B?TWFoZXNoIEJhbmRld2FyICjgpK7gpLngpYfgpLYg4KSs4KSC4KSh4KWH4KS14KS+4KSwKQ==?= <maheshb@google.com>
Date: Fri, 5 Jan 2024 09:51:40 -0800
Message-ID: <CAF2d9jga9oc4OST6PMU=C9rz_NDrURCcLGx-1tP31U00z63vbA@mail.gmail.com>
Subject: Re: [PATCHv3 net-next 2/3] ptp: add ioctl interface for ptp_gettimex64any()
To: Richard Cochran <richardcochran@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>, Linux <linux-kernel@vger.kernel.org>, 
	David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, 
	Eric Dumazet <edumazet@google.com>, Paolo Abeni <pabeni@redhat.com>, 
	Jonathan Corbet <corbet@lwn.net>, John Stultz <jstultz@google.com>, Don Hatchett <hatch@google.com>, 
	Yuliang Li <yuliangli@google.com>, Mahesh Bandewar <mahesh@bandewar.net>, 
	Willem de Bruijn <willemb@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 4, 2024 at 2:37=E2=80=AFPM Richard Cochran <richardcochran@gmai=
l.com> wrote:
>
> On Thu, Jan 04, 2024 at 01:24:39PM -0800, Mahesh Bandewar wrote:
>
> > @@ -226,6 +238,8 @@ struct ptp_pin_desc {
> >       _IOWR(PTP_CLK_MAGIC, 18, struct ptp_sys_offset_extended)
> >  #define PTP_MASK_CLEAR_ALL  _IO(PTP_CLK_MAGIC, 19)
> >  #define PTP_MASK_EN_SINGLE  _IOW(PTP_CLK_MAGIC, 20, unsigned int)
> > +#define PTP_SYS_OFFSET_ANY \
> > +     _IOWR(PTP_CLK_MAGIC, 21, struct ptp_sys_offset_any)
>
> As I said before, this functionality really ought to be a new system call=
.
>
> Did you see these patch series posted on the list?
>
>  31.Dec'23 Sagi Maimon          [PATCH v4] posix-timers: add multi_clock_=
gettime system call
>  31.Dec'23 Andy Lutomirski      =E2=94=9C=E2=94=80>
>  01.Jan'24 Sagi Maimon          =E2=94=82 =E2=94=94=E2=94=80>
>  01.Jan'24 kernel test rob      =E2=94=9C=E2=94=80>
>  01.Jan'24 kernel test rob      =E2=94=94=E2=94=80>
>
>  02.Jan'24 Sagi Maimon          [PATCH v5] posix-timers: add multi_clock_=
gettime system call
>  02.Jan'24 Arnd Bergmann        =E2=94=9C=E2=94=80>
>  03.Jan'24 Sagi Maimon          =E2=94=82 =E2=94=94=E2=94=80>
>  04.Jan'24 kernel test rob      =E2=94=94=E2=94=80>
>
> I think this will be the way forward.
>
> Please review the multi_clock_gettime series and help refine it.
>

While multi_clock_gettime streamlines POSIX clock reads (defined in
posix-timers.h: struct k_time), this proposal targets precision
enhancements for PTP hardware clocks (defined in ptp_clock_kernel.h:
struct ptp_clock_info).

Key distinctions:
       1. Target clocks: multi_clock_gettime operates on POSIX clocks
(posix-timers.h), while this proposal focuses on PTP hardware clocks
(ptp_clock_kernel.h).
       2. Purpose: multi_clock_gettime addresses scheduling latencies
by consolidating multiple clock reads. This proposal aims to enhance
PTP clock-read precision by measuring syscall width.

POSIX clocks are employed in this series for syscall width
measurement, potentially leading to misunderstandings about
overlapping functionality. However, their roles are distinct and serve
different purposes.
Both approaches address time-related challenges, but with different
goals and techniques.
multi_clock_gettime optimizes scheduling efficiency for POSIX clocks,
while this proposal refines PTP hardware clock-read accuracy.
They complement each other, catering to diverse application needs
within the timekeeping domain.

Hope this helps.

Thanks,
--mahesh..

> Thanks,
> Richard
>