From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 3/3] net/e1000: initialize PTP to system time
Date: Tue, 26 Nov 2024 08:30:25 +0000 [thread overview]
Message-ID: <MW4PR11MB5912DBC7B0B570E5E3A11A3E9F2F2@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <fad5aa89864c290993917712d7cff64a5f317c68.1732534388.git.anatoly.burakov@intel.com>
> -----Original Message-----
> From: Anatoly Burakov <anatoly.burakov@intel.com>
> Sent: Monday, November 25, 2024 7:33 PM
> To: dev@dpdk.org
> Subject: [PATCH v2 3/3] net/e1000: initialize PTP to system time
>
> 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>
> ---
Tested-by: Hailin Xu <hailinx.xu@intel.com>
next prev parent reply other threads:[~2024-11-26 8:30 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 [this message]
2024-11-26 15:44 ` Bruce Richardson
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=MW4PR11MB5912DBC7B0B570E5E3A11A3E9F2F2@MW4PR11MB5912.namprd11.prod.outlook.com \
--to=hailinx.xu@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).