From: Paolo Abeni <pabeni@redhat.com>
To: Mahesh Bandewar <maheshb@google.com>,
Netdev <netdev@vger.kernel.org>, Tariq Toukan <tariqt@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>
Cc: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Richard Cochran <richardcochran@gmail.com>,
Mahesh Bandewar <mahesh@bandewar.net>
Subject: Re: [PATCH net-next 1/2] mlx4: update mlx4_clock_read() to provide pre/post tstamps
Date: Thu, 10 Oct 2024 10:44:14 +0200 [thread overview]
Message-ID: <9b36bb45-a31c-4cf7-a6af-cd77cc55e011@redhat.com> (raw)
In-Reply-To: <749706b1-f44a-4548-9573-5f7b3823be67@redhat.com>
On 10/10/24 10:36, Paolo Abeni wrote:
> On 10/8/24 12:46, Mahesh Bandewar wrote:
>> The mlx4_clock_read() function, when called by cycle_counter->read(),
>> previously only returned the raw cycle count. However, for PTP helpers
>> like gettimex64(), which require pre- and post-timestamps, simply
>> returning raw cycles is insufficient. It also needs to provide the
>> necessary timestamps.
>>
>> This update modifies mlx4_clock_read() to return both the cycles and
>> the required timestamps. Additionally, mlx4_en_read_clock() is now
>> responsible for reading and updating the clock_cache. This allows
>> another function, mlx4_en_read_clock_cache(), to act as the cycle
>> reader for cycle_counter->read(), preserving the same interface.
>
> It looks like this patch should be split in two, the first one could be
> possibly 'net' material and just fix gettimex64()/mlx4_read_clock() and
> the other one introduces the cache.
My bad, I was too hasty and actually missed that the gettimex64()
callback is implemented in the next patch.
The main point still remains: the cache infra should be in a separate
patch: it can introduce side effects and we want to be able to bisect.
Thanks,
Paolo
next prev parent reply other threads:[~2024-10-10 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 10:46 [PATCH net-next 1/2] mlx4: update mlx4_clock_read() to provide pre/post tstamps Mahesh Bandewar
2024-10-10 8:36 ` Paolo Abeni
2024-10-10 8:44 ` Paolo Abeni [this message]
2024-10-12 7:03 ` Mahesh Bandewar (महेश बंडेवार)
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=9b36bb45-a31c-4cf7-a6af-cd77cc55e011@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tariqt@nvidia.com \
--cc=yishaih@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).