DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v2 3/3] net/e1000: initialize PTP to system time
Date: Tue, 26 Nov 2024 15:44:33 +0000	[thread overview]
Message-ID: <Z0Xs4Q6Xtw_YJjHs@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <fad5aa89864c290993917712d7cff64a5f317c68.1732534388.git.anatoly.burakov@intel.com>

On Mon, Nov 25, 2024 at 11:33:26AM +0000, Anatoly Burakov wrote:
> Currently, e1000 driver initializes PTP timestamp to 0. This is different
> from what kernel driver does (which initializes it to system time).
> 
> Align the DPDK driver to kernel driver by setting PTP timestamp to system
> time when enabling PTP.
> 
> Note that e1000 driver always uses zero-based timestamps for PTP, so we
> would only ever update the internal timecounter and not the actual NIC
> registers.
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  parent reply	other threads:[~2024-11-26 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 15:18 [PATCH v1 1/3] net/ixgbe: " Anatoly Burakov
2024-11-22 15:18 ` [PATCH v1 2/3] net/i40e: " Anatoly Burakov
2024-11-22 15:18 ` [PATCH v1 3/3] net/e1000: " Anatoly Burakov
2024-11-25 11:33 ` [PATCH v2 1/3] net/ixgbe: " Anatoly Burakov
2024-11-25 11:33   ` [PATCH v2 2/3] net/i40e: " Anatoly Burakov
2024-11-26 15:44     ` Bruce Richardson
2024-11-25 11:33   ` [PATCH v2 3/3] net/e1000: " Anatoly Burakov
2024-11-26  8:30     ` Xu, HailinX
2024-11-26 15:44     ` Bruce Richardson [this message]
2024-11-26  8:30   ` [PATCH v2 1/3] net/ixgbe: " Xu, HailinX
2024-11-26 15:43   ` Bruce Richardson
2024-11-26 16:09   ` Bruce Richardson

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=Z0Xs4Q6Xtw_YJjHs@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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).