All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
Cc: intel-wired-lan@osuosl.org, edumazet@google.com,
	netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	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: Tue, 27 Sep 2022 17:27:27 +0200	[thread overview]
Message-ID: <YzMWX1xPC0NChKNl@lunn.ch> (raw)
In-Reply-To: <20220927130656.32567-1-muhammad.husaini.zulkifli@intel.com>

On Tue, Sep 27, 2022 at 09:06:52PM +0800, Muhammad Husaini Zulkifli wrote:
> The HW TX timestamps created by the NIC via socket options can be
> requested using the current network timestamps generation capability of
> SOF_TIMESTAMPING_TX_HARDWARE. The most common users of this socket flag
> is PTP, however other packet applications that require tx timestamps might
> also ask for it.
> 
> The problem is that, when there is a lot of traffic, there is a high chance
> that the timestamps for a PTP packet will be lost if both PTP and Non-PTP
> packets use the same SOF TIMESTAMPING TX HARDWARE causing the tx timeout.
> 
> DMA timestamps through socket options are not currently available to
> the user. Because if the user wants to, they can configure the hwtstamp
> config option to use the new introduced DMA Time Stamp flag through the
> setsockopt().
> 
> With these additional socket options, users can continue to utilise
> HW timestamps for PTP while specifying non-PTP packets to use DMA
> timestamps if the NIC can support them.

Although this is not actually for PTP, you probably should Cc: the PTP
maintainer for patches like this.

	   Andrew
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
Cc: intel-wired-lan@osuosl.org, netdev@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
	vinicius.gomes@intel.com, aravindhan.gunasekaran@intel.com,
	noor.azura.ahmad.tarmizi@intel.com
Subject: Re: [PATCH v1 0/4] Add support for DMA timestamp for non-PTP packets
Date: Tue, 27 Sep 2022 17:27:27 +0200	[thread overview]
Message-ID: <YzMWX1xPC0NChKNl@lunn.ch> (raw)
In-Reply-To: <20220927130656.32567-1-muhammad.husaini.zulkifli@intel.com>

On Tue, Sep 27, 2022 at 09:06:52PM +0800, Muhammad Husaini Zulkifli wrote:
> The HW TX timestamps created by the NIC via socket options can be
> requested using the current network timestamps generation capability of
> SOF_TIMESTAMPING_TX_HARDWARE. The most common users of this socket flag
> is PTP, however other packet applications that require tx timestamps might
> also ask for it.
> 
> The problem is that, when there is a lot of traffic, there is a high chance
> that the timestamps for a PTP packet will be lost if both PTP and Non-PTP
> packets use the same SOF TIMESTAMPING TX HARDWARE causing the tx timeout.
> 
> DMA timestamps through socket options are not currently available to
> the user. Because if the user wants to, they can configure the hwtstamp
> config option to use the new introduced DMA Time Stamp flag through the
> setsockopt().
> 
> With these additional socket options, users can continue to utilise
> HW timestamps for PTP while specifying non-PTP packets to use DMA
> timestamps if the NIC can support them.

Although this is not actually for PTP, you probably should Cc: the PTP
maintainer for patches like this.

	   Andrew

  parent reply	other threads:[~2022-09-27 15:27 UTC|newest]

Thread overview: 32+ 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 ` 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-27 13:06   ` Muhammad Husaini Zulkifli
2022-09-28  0:11   ` [Intel-wired-lan] " Jakub Kicinski
2022-09-28  0:11     ` Jakub Kicinski
2022-09-29  3:40     ` [Intel-wired-lan] " Zulkifli, Muhammad Husaini
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   ` 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   ` 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 13:06   ` Muhammad Husaini Zulkifli
2022-09-27 15:27 ` Andrew Lunn [this message]
2022-09-27 15:27   ` [PATCH v1 0/4] " Andrew Lunn
2022-09-29  2:22   ` [Intel-wired-lan] " Zulkifli, Muhammad Husaini
2022-09-29  2:22     ` Zulkifli, Muhammad Husaini
2022-09-28  0:09 ` [Intel-wired-lan] " Jakub Kicinski
2022-09-28  0:09   ` Jakub Kicinski
2022-09-29  2:35   ` [Intel-wired-lan] " Zulkifli, Muhammad Husaini
2022-09-29  2:35     ` Zulkifli, Muhammad Husaini
2022-09-29 13:56     ` [Intel-wired-lan] " Jakub Kicinski
2022-09-29 13:56       ` Jakub Kicinski
2022-09-29 14:46       ` [Intel-wired-lan] " Gal Pressman
2022-09-29 14:46         ` Gal Pressman
2022-09-29 15:23         ` [Intel-wired-lan] " Jakub Kicinski
2022-09-29 15:23           ` Jakub Kicinski
2022-09-30  8:52       ` [Intel-wired-lan] " Zulkifli, Muhammad Husaini
2022-09-30  8:52         ` Zulkifli, Muhammad Husaini
2022-09-30 14:40         ` [Intel-wired-lan] " Jakub Kicinski
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=YzMWX1xPC0NChKNl@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@osuosl.org \
    --cc=kuba@kernel.org \
    --cc=muhammad.husaini.zulkifli@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=noor.azura.ahmad.tarmizi@intel.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.