[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZR/pN0Ll5VVNpL4m@kernel.org>
Date: Fri, 6 Oct 2023 13:02:15 +0200
From: Simon Horman <horms@...nel.org>
To: Xabier Marquiegui <reibax@...il.com>
Cc: netdev@...r.kernel.org, richardcochran@...il.com, tglx@...utronix.de,
jstultz@...gle.com, chrony-dev@...ony.tuxfamily.org,
mlichvar@...hat.com, ntp-lists@...tcorallo.com,
vinicius.gomes@...el.com, alex.maftei@....com, davem@...emloft.net,
rrameshbabu@...dia.com, shuah@...nel.org
Subject: Re: [PATCH net-next v4 1/6] posix-clock: introduce
posix_clock_context concept
On Thu, Oct 05, 2023 at 03:53:11PM +0200, Xabier Marquiegui wrote:
> Add the necessary structure to support custom private-data per
> posix-clock user.
>
> The previous implementation of posix-clock assumed all file open
> instances need access to the same clock structure on private_data.
>
> The need for individual data structures per file open instance has been
> identified when developing support for multiple timestamp event queue
> users for ptp_clock.
>
> This patch introduces a generic posix_clock_context data structure as a
> solution to that, and simmilar problems.
nit: similar
Powered by blists - more mailing lists