All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
	intel-wired-lan@lists.osuosl.org, horms@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 00/12] Add support for Rx timestamping for both ice and iavf drivers.
Date: Thu, 18 Apr 2024 13:19:09 -0700	[thread overview]
Message-ID: <87v84ectez.fsf@nvidia.com> (raw)
In-Reply-To: <20240418052500.50678-1-mateusz.polchlopek@intel.com>


On Thu, 18 Apr, 2024 01:24:48 -0400 Mateusz Polchlopek <mateusz.polchlopek@intel.com> 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 SIOCSHWTSTAMP ioctl,
> 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.
>
> ---

Just one general/cosmetic comment. It might make more sense for the
Reviewed-by: trailer to come after the Signed-off-by: trailer, since the
review happens after the patches have been written.

--
Thanks,

Rahul Rameshbabu

WARNING: multiple messages have this Message-ID (diff)
From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	horms@kernel.org, anthony.l.nguyen@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 00/12] Add support for Rx timestamping for both ice and iavf drivers.
Date: Thu, 18 Apr 2024 13:19:09 -0700	[thread overview]
Message-ID: <87v84ectez.fsf@nvidia.com> (raw)
In-Reply-To: <20240418052500.50678-1-mateusz.polchlopek@intel.com>


On Thu, 18 Apr, 2024 01:24:48 -0400 Mateusz Polchlopek <mateusz.polchlopek@intel.com> 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 SIOCSHWTSTAMP ioctl,
> 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.
>
> ---

Just one general/cosmetic comment. It might make more sense for the
Reviewed-by: trailer to come after the Signed-off-by: trailer, since the
review happens after the patches have been written.

--
Thanks,

Rahul Rameshbabu

  parent reply	other threads:[~2024-04-18 20:22 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  5:24 [Intel-wired-lan] [PATCH iwl-next v5 00/12] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-04-18  5:24 ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 01/12] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 18:49   ` Rahul Rameshbabu
2024-04-18 18:49     ` Rahul Rameshbabu
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 02/12] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 18:57   ` Rahul Rameshbabu
2024-04-18 18:57     ` Rahul Rameshbabu
2024-04-22  9:34     ` Mateusz Polchlopek
2024-04-22  9:34       ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 03/12] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:05   ` Rahul Rameshbabu
2024-04-18 19:05     ` Rahul Rameshbabu
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 04/12] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:11   ` Rahul Rameshbabu
2024-04-18 19:11     ` Rahul Rameshbabu
2024-04-22  9:34     ` Mateusz Polchlopek
2024-04-22  9:34       ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 05/12] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:16   ` Rahul Rameshbabu
2024-04-18 19:16     ` Rahul Rameshbabu
2024-04-22  9:33     ` Mateusz Polchlopek
2024-04-22  9:33       ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 06/12] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:28   ` Rahul Rameshbabu
2024-04-18 19:28     ` Rahul Rameshbabu
2024-04-22  9:29     ` Mateusz Polchlopek
2024-04-22  9:29       ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 07/12] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:43   ` Rahul Rameshbabu
2024-04-18 19:43     ` Rahul Rameshbabu
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 08/12] iavf: periodically cache " Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 19:51   ` Rahul Rameshbabu
2024-04-18 19:51     ` Rahul Rameshbabu
2024-04-22  9:23     ` Mateusz Polchlopek
2024-04-22  9:23       ` Mateusz Polchlopek
2024-04-24 22:03       ` Keller, Jacob E
2024-04-24 22:03         ` Keller, Jacob E
2024-04-25 10:52         ` Przemek Kitszel
2024-04-25 10:52           ` Przemek Kitszel
2024-04-25 16:28           ` Keller, Jacob E
2024-04-25 16:28             ` Keller, Jacob E
2024-04-25 17:10             ` Rahul Rameshbabu
2024-04-25 17:10               ` Rahul Rameshbabu
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 20:00   ` Rahul Rameshbabu
2024-04-18 20:00     ` Rahul Rameshbabu
2024-04-22  9:22     ` Mateusz Polchlopek
2024-04-22  9:22       ` Mateusz Polchlopek
2024-04-23 10:51   ` Sunil Kovvuri Goutham
2024-04-23 10:51     ` Sunil Kovvuri Goutham
2024-04-26  7:15     ` Mateusz Polchlopek
2024-04-26  7:15       ` Mateusz Polchlopek
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 10/12] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 20:07   ` Rahul Rameshbabu
2024-04-18 20:07     ` Rahul Rameshbabu
2024-04-18  5:24 ` [Intel-wired-lan] [PATCH iwl-next v5 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP Mateusz Polchlopek
2024-04-18  5:24   ` Mateusz Polchlopek
2024-04-18 20:08   ` Rahul Rameshbabu
2024-04-18 20:08     ` Rahul Rameshbabu
2024-04-18  5:25 ` [Intel-wired-lan] [PATCH iwl-next v5 12/12] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-04-18  5:25   ` Mateusz Polchlopek
2024-04-18 20:12   ` Rahul Rameshbabu
2024-04-18 20:12     ` Rahul Rameshbabu
2024-04-23 10:47   ` Sunil Kovvuri Goutham
2024-04-23 10:47     ` Sunil Kovvuri Goutham
2024-04-18 20:19 ` Rahul Rameshbabu [this message]
2024-04-18 20:19   ` [Intel-wired-lan] [PATCH iwl-next v5 00/12] Add support for Rx timestamping for both ice and iavf drivers Rahul Rameshbabu
2024-04-22  9:37   ` Mateusz Polchlopek
2024-04-22  9:37     ` Mateusz Polchlopek
2024-04-23  5:57     ` Rahul Rameshbabu
2024-04-23  5:57       ` Rahul Rameshbabu
2024-04-23  6:08       ` Mateusz Polchlopek
2024-04-23  6:08         ` Mateusz Polchlopek

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=87v84ectez.fsf@nvidia.com \
    --to=rrameshbabu@nvidia.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=horms@kernel.org \
    --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 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.