All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Miroslav Lichvar <mlichvar@redhat.com>,
	intel-wired-lan@lists.osuosl.org, andre.guedes@intel.com,
	linux-pci@vger.kernel.org, netdev@vger.kernel.org,
	bhelgaas@google.com
Subject: Re: [Intel-wired-lan] [PATCH next-queue v2 3/3] igc: Add support for PTP getcrosststamp()
Date: Mon, 16 Nov 2020 17:06:30 -0800	[thread overview]
Message-ID: <874klo7pwp.fsf@intel.com> (raw)
In-Reply-To: <20201114025704.GA15240@hoboy.vegasvil.org>

Hi Richard,

Richard Cochran <richardcochran@gmail.com> writes:

> What is a PTM?  Why does a PTM have dialogs?  Can it talk?
>
> Forgive my total ignorance!

:-)

We are talking about PCIe PTM (Precise Time Measurement), basically it's
a PTP-like protocol running on the PCIe fabric.

The PTM dialogs are a pair of messages: a Request from the endpoint (in
my case, the NIC) to the PCIe root (or switch), and a Response from the
other side (this message includes the Master Root Time, and the
calculated propagation delay).

The interface exposed by the NIC I have allows basically to start/stop
these PTM dialogs (I was calling them PTM cycles) and to configure the
interval between each cycle (~1ms - ~512ms).

I also have access to four time stamps:
 - T1, when the NIC sends the Request message;
 - T2, when the PCIe root received the Request message;
 - T3, when the PCIe root sends the Response message;
 - T4, when the NIC receives the Response message;

Actually, I have T1 (on this cycle), T2 (on this and on the previous
cycle), 'T4 - T1' (on this and on the previous cycle) and 'T3 - T2' (on
the previous cycle).

Another thing of note, is that trying to start the PTM dialogs "on
demand" syncronously with the ioctl() doesn't seem too reliable, it
seems to want to be kept running for a longer time.

I think that's it for a "PCIe PTM from a software person" overview :-)


Cheers,
-- 
Vinicius

WARNING: multiple messages have this Message-ID (diff)
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH next-queue v2 3/3] igc: Add support for PTP getcrosststamp()
Date: Mon, 16 Nov 2020 17:06:30 -0800	[thread overview]
Message-ID: <874klo7pwp.fsf@intel.com> (raw)
In-Reply-To: <20201114025704.GA15240@hoboy.vegasvil.org>

Hi Richard,

Richard Cochran <richardcochran@gmail.com> writes:

> What is a PTM?  Why does a PTM have dialogs?  Can it talk?
>
> Forgive my total ignorance!

:-)

We are talking about PCIe PTM (Precise Time Measurement), basically it's
a PTP-like protocol running on the PCIe fabric.

The PTM dialogs are a pair of messages: a Request from the endpoint (in
my case, the NIC) to the PCIe root (or switch), and a Response from the
other side (this message includes the Master Root Time, and the
calculated propagation delay).

The interface exposed by the NIC I have allows basically to start/stop
these PTM dialogs (I was calling them PTM cycles) and to configure the
interval between each cycle (~1ms - ~512ms).

I also have access to four time stamps:
 - T1, when the NIC sends the Request message;
 - T2, when the PCIe root received the Request message;
 - T3, when the PCIe root sends the Response message;
 - T4, when the NIC receives the Response message;

Actually, I have T1 (on this cycle), T2 (on this and on the previous
cycle), 'T4 - T1' (on this and on the previous cycle) and 'T3 - T2' (on
the previous cycle).

Another thing of note, is that trying to start the PTM dialogs "on
demand" syncronously with the ioctl() doesn't seem too reliable, it
seems to want to be kept running for a longer time.

I think that's it for a "PCIe PTM from a software person" overview :-)


Cheers,
-- 
Vinicius

  reply	other threads:[~2020-11-17  1:06 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  6:10 [PATCH next-queue v2 0/3] igc: Add support for PCIe PTM Vinicius Costa Gomes
2020-11-10  6:10 ` [Intel-wired-lan] " Vinicius Costa Gomes
2020-11-10  6:10 ` [PATCH next-queue v2 1/3] Revert "PCI: Make pci_enable_ptm() private" Vinicius Costa Gomes
2020-11-10  6:10   ` [Intel-wired-lan] " Vinicius Costa Gomes
2020-11-10  6:10 ` [PATCH next-queue v2 2/3] igc: Enable PCIe PTM Vinicius Costa Gomes
2020-11-10  6:10   ` [Intel-wired-lan] " Vinicius Costa Gomes
2020-11-10  6:10 ` [PATCH next-queue v2 3/3] igc: Add support for PTP getcrosststamp() Vinicius Costa Gomes
2020-11-10  6:10   ` [Intel-wired-lan] " Vinicius Costa Gomes
2020-11-10 18:07   ` Miroslav Lichvar
2020-11-10 18:07     ` Miroslav Lichvar
2020-11-10 19:06     ` Vinicius Costa Gomes
2020-11-10 19:06       ` Vinicius Costa Gomes
2020-11-11  9:33       ` Miroslav Lichvar
2020-11-11  9:33         ` Miroslav Lichvar
2020-11-11 22:23         ` Vinicius Costa Gomes
2020-11-11 22:23           ` Vinicius Costa Gomes
2020-11-12  9:32           ` Miroslav Lichvar
2020-11-12  9:32             ` Miroslav Lichvar
2020-11-12 23:46             ` Vinicius Costa Gomes
2020-11-12 23:46               ` Vinicius Costa Gomes
2020-11-13  3:24               ` Richard Cochran
2020-11-13  3:24                 ` Richard Cochran
2020-11-13 19:10                 ` Vinicius Costa Gomes
2020-11-13 19:10                   ` Vinicius Costa Gomes
2020-11-14  2:57                   ` Richard Cochran
2020-11-14  2:57                     ` Richard Cochran
2020-11-17  1:06                     ` Vinicius Costa Gomes [this message]
2020-11-17  1:06                       ` Vinicius Costa Gomes
2020-11-17  1:49                       ` Richard Cochran
2020-11-17  1:49                         ` Richard Cochran
2020-11-18  1:21                         ` Vinicius Costa Gomes
2020-11-18  1:21                           ` Vinicius Costa Gomes
2020-11-18 12:54                           ` Richard Cochran
2020-11-18 12:54                             ` Richard Cochran
2020-11-19  0:22                             ` Vinicius Costa Gomes
2020-11-19  0:22                               ` Vinicius Costa Gomes
2020-11-20 14:16                               ` Richard Cochran
2020-11-20 14:16                                 ` Richard Cochran
2020-11-20 17:58                                 ` Vinicius Costa Gomes
2020-11-20 17:58                                   ` Vinicius Costa Gomes
2021-03-22 15:36                             ` Vinicius Costa Gomes
2021-03-22 15:36                               ` Vinicius Costa Gomes
2021-03-23  4:17                               ` Richard Cochran
2021-03-23  4:17                                 ` Richard Cochran
2020-11-18 15:55                           ` Jakub Kicinski
2020-11-18 15:55                             ` Jakub Kicinski
2020-11-20 19:07                             ` Vinicius Costa Gomes
2020-11-20 19:07                               ` Vinicius Costa Gomes
2020-11-12  0:38     ` Vinicius Costa Gomes
2020-11-12  0:38       ` Vinicius Costa Gomes
2021-03-22 15:47     ` Vinicius Costa Gomes
2021-03-22 15:47       ` Vinicius Costa Gomes

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=874klo7pwp.fsf@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=andre.guedes@intel.com \
    --cc=bhelgaas@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mlichvar@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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 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.