Received-SPF: pass (google.com: domain of linux-kernel+bounces-19386-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Thomas Gleixner <tglx@linutronix.de>
To: Sagi Maimon <maimon.sagi@gmail.com>, richardcochran@gmail.com,
 luto@kernel.org, datglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
 dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, arnd@arndb.de,
 geert@linux-m68k.org, peterz@infradead.org, hannes@cmpxchg.org,
 sohil.mehta@intel.com, rick.p.edgecombe@intel.com, nphamcs@gmail.com,
 palmer@sifive.com, maimon.sagi@gmail.com, keescook@chromium.org,
 legion@kernel.org, mark.rutland@arm.com
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
 linux-arch@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v5] posix-timers: add multi_clock_gettime system call
In-Reply-To: <20240102091855.70418-1-maimon.sagi@gmail.com>
References: <20240102091855.70418-1-maimon.sagi@gmail.com>
Date: Mon, 08 Jan 2024 12:09:00 +0100
Message-ID: <875y04kroz.ffs@tglx>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

On Tue, Jan 02 2024 at 11:18, Sagi Maimon wrote:
> Some user space applications need to read some clocks.
> Each read requires moving from user space to kernel space.
> The syscall overhead causes unpredictable delay between N clocks reads
> Removing this delay causes better synchronization between N clocks.

As I explained to you before: This is wishful thinking.

There is absolutely no guarantee that the syscall will yield better
results. It might on average, but that's a useless measure.

You also still fail to explain what this is going to solve and how it's
used.

> Some user space applications need to read some clocks.

Is just not an explanation at all.

Thanks,

        tglx