From: Jacob Keller <jacob.e.keller@intel.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
<intel-wired-lan@lists.osuosl.org>,
<aleksander.lobakin@intel.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v11 00/14] Add support for Rx timestamping for both ice and iavf drivers
Date: Fri, 18 Oct 2024 15:34:18 -0700 [thread overview]
Message-ID: <ae6c51ea-3479-4be2-b955-10895a8f8a38@intel.com> (raw)
In-Reply-To: <20241013154415.20262-1-mateusz.polchlopek@intel.com>
On 10/13/2024 8:44 AM, Mateusz Polchlopek wrote:
> Initially, during VF creation it registers the PTP clock in
> the system and negotiates with PF it's capabilities. In the
> meantime the PF enables the Flexible Descriptor for VF.
> Only this type of descriptor allows to receive Rx timestamps.
>
> Enabling virtual clock would be possible, though it would probably
> perform poorly due to the lack of direct time access.
>
> Enable timestamping should be done using userspace tools, e.g.
> hwstamp_ctl -i $VF -r 14
>
> In order to report the timestamps to userspace, the VF extends
> timestamp to 40b.
>
> To support this feature the flexible descriptors and PTP part
> in iavf driver have been introduced.
>
> Side notes:
> Wojtek did great job handling this series during my vacations. Thanks!
> ---
> v11:
> - addressed all comments from v10 done by Alexander L. Short list: changed some
> logging functions (like pci_warn instead of dev_warn), fix RCT, fix indentation,
> remove unnecessary comments and casts, change error codes where applicable,
> remove ptp.initialized field in struct (now check for ptp.clock as Olek
> suggested), invert condition in few places to avoid +1 indent level, function
> iavf_ptp_do_aux_work made as static, add more descriptive kdoc for libeth
> struct fields, restore ptype as a field in libeth struct, remove unused
> defines, pass to specific functions quad word of descriptor instead of pass
> rx_desc, add asserts to structs where applicable, return from fields extracting
> functions when !fields.eop, refactor get VLAN tags, remove unnecessary empty
> initialization of structs and few more. Please see v10 to compare all changes.
>
Unfortunately, v11 doesn't compile. Can you please address that in a
v12? While at it, please also address the concern about the post_ts
calls in the .gettimex implementation.
Thanks,
Jake
prev parent reply other threads:[~2024-10-18 22:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 15:44 [Intel-wired-lan] [PATCH iwl-next v11 00/14] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 01/14] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 02/14] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 03/14] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 04/14] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 05/14] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 06/14] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 07/14] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-10-15 13:56 ` Vadim Fedorenko
2024-10-15 19:24 ` Keller, Jacob E
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 08/14] iavf: periodically cache " Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 09/14] libeth: move idpf_rx_csum_decoded and idpf_rx_extracted Mateusz Polchlopek
2024-10-15 16:41 ` kernel test robot
2024-10-15 18:03 ` kernel test robot
2024-10-18 22:31 ` Jacob Keller
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 10/14] iavf: define Rx descriptors as qwords Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 11/14] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 12/14] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 13/14] iavf: handle set and get timestamps ops Mateusz Polchlopek
2024-10-13 15:44 ` [Intel-wired-lan] [PATCH iwl-next v11 14/14] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-10-18 22:34 ` Jacob Keller [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=ae6c51ea-3479-4be2-b955-10895a8f8a38@intel.com \
--to=jacob.e.keller@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.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 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).