Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: "leon@kernel.org" <leon@kernel.org>,
	"intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>,
	Richard Cochran <richardcochran@gmail.com>,
	Saeed Mahameed <saeed@kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Michael Chan <michael.chan@broadcom.com>,
	"Zulkifli,
	Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	Andy Gospodarek <andy@greyhouse.net>,
	"Ahmad Tarmizi, Noor Azura" <noor.azura.ahmad.tarmizi@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v1 0/4] Add support for DMA timestamp for non-PTP packets
Date: Thu, 29 Sep 2022 08:23:27 -0700	[thread overview]
Message-ID: <20220929082327.209d6227@kernel.org> (raw)
In-Reply-To: <6f6f4487-1c5d-de4e-0c79-452128deae0c@nvidia.com>

On Thu, 29 Sep 2022 17:46:04 +0300 Gal Pressman wrote:
> What exactly do you mean by DMA stamps?
> 
> Our NIC supports two modes of operation (both TX/RX):
> - CQE timestamp (I think that's what you call DMA timestamp), where the
> timestamp is written when the completion is being written/generated.
> - Port timestamp (MAC timestamp), where the timstamp is written when the
> packet is being sent to the wire, or received from the wire. This
> doesn't account for the time the packet spent inside the NIC pipeline.
> 
> So I believe the answer to your question is yes :).

Thanks! I think we should provide the config API for both Tx and Rx,
then.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-09-29 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 13:06 [Intel-wired-lan] [PATCH v1 0/4] Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-09-27 13:06 ` [Intel-wired-lan] [PATCH v1 1/4] ethtool: Add new hwtstamp flag Muhammad Husaini Zulkifli
2022-09-28  0:11   ` Jakub Kicinski
2022-09-29  3:40     ` Zulkifli, Muhammad Husaini
2022-09-27 13:06 ` [Intel-wired-lan] [PATCH v1 2/4] net-timestamp: Increase the size of tsflags Muhammad Husaini Zulkifli
2022-09-27 13:06 ` [Intel-wired-lan] [PATCH v1 3/4] net: sock: extend SO_TIMESTAMPING for DMA Fetch Muhammad Husaini Zulkifli
2022-09-27 13:06 ` [Intel-wired-lan] [PATCH v1 4/4] igc: Add support for DMA timestamp for non-PTP packets Muhammad Husaini Zulkifli
2022-09-27 15:27 ` [Intel-wired-lan] [PATCH v1 0/4] " Andrew Lunn
2022-09-29  2:22   ` Zulkifli, Muhammad Husaini
2022-09-28  0:09 ` Jakub Kicinski
2022-09-29  2:35   ` Zulkifli, Muhammad Husaini
2022-09-29 13:56     ` Jakub Kicinski
2022-09-29 14:46       ` Gal Pressman
2022-09-29 15:23         ` Jakub Kicinski [this message]
2022-09-30  8:52       ` Zulkifli, Muhammad Husaini
2022-09-30 14:40         ` Jakub Kicinski

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=20220929082327.209d6227@kernel.org \
    --to=kuba@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=leon@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=muhammad.husaini.zulkifli@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=noor.azura.ahmad.tarmizi@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=saeed@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