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
Date: Mon, 08 Jan 2024 12:09:00 +0100 [thread overview]
Message-ID: <875y04kroz.ffs@tglx> (raw)
In-Reply-To: <20240102091855.70418-1-maimon.sagi@gmail.com>
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
prev parent reply other threads:[~2024-01-08 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 9:18 [PATCH v5] posix-timers: add multi_clock_gettime system call Sagi Maimon
2024-01-02 10:21 ` Arnd Bergmann
2024-01-03 12:59 ` Sagi Maimon
2024-01-04 3:06 ` kernel test robot
2024-01-08 11:09 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y04kroz.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=datglx@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=legion@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maimon.sagi@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nphamcs@gmail.com \
--cc=palmer@sifive.com \
--cc=peterz@infradead.org \
--cc=richardcochran@gmail.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sohil.mehta@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.