From: Bruce Richardson <bruce.richardson@intel.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>
Cc: "Hore, Soumyadeep" <soumyadeep.hore@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
"Subbarao, Manoj Kumar" <manoj.kumar.subbarao@intel.com>
Subject: Re: [PATCH v4 2/6] net/intel: add read clock feature in ICE
Date: Thu, 12 Jun 2025 16:48:35 +0100 [thread overview]
Message-ID: <aEr202MXrf3Mnsm-@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <DM3PPF7D18F34A1A5202037B5AB7DC9F6948E74A@DM3PPF7D18F34A1.namprd11.prod.outlook.com>
On Thu, Jun 12, 2025 at 11:14:30AM +0100, Loftus, Ciara wrote:
> > Subject: [PATCH v4 2/6] net/intel: add read clock feature in ICE
>
> Since the change is specific to the ice driver only, I think the title should change to "net/ice" and you can drop the mention of "in ICE" in the message that follows the colon.
>
> >
> > Adding eth_ice_read_clock() feature to get current time
> > for scheduling Packets based on Tx time.
> >
> > Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
> > ---
> > drivers/net/intel/ice/ice_ethdev.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/drivers/net/intel/ice/ice_ethdev.c
> > b/drivers/net/intel/ice/ice_ethdev.c
> > index 7cc083ca32..9478ba92df 100644
> > --- a/drivers/net/intel/ice/ice_ethdev.c
> > +++ b/drivers/net/intel/ice/ice_ethdev.c
> > @@ -187,6 +187,7 @@ static int ice_timesync_read_time(struct rte_eth_dev
> > *dev,
> > static int ice_timesync_write_time(struct rte_eth_dev *dev,
> > const struct timespec *timestamp);
> > static int ice_timesync_disable(struct rte_eth_dev *dev);
> > +static int eth_ice_read_clock(struct rte_eth_dev *dev, uint64_t *clock);
> > static int ice_fec_get_capability(struct rte_eth_dev *dev, struct
> > rte_eth_fec_capa *speed_fec_capa,
> > unsigned int num);
> > static int ice_fec_get(struct rte_eth_dev *dev, uint32_t *fec_capa);
> > @@ -317,6 +318,7 @@ static const struct eth_dev_ops ice_eth_dev_ops = {
> > .timesync_read_time = ice_timesync_read_time,
> > .timesync_write_time = ice_timesync_write_time,
> > .timesync_disable = ice_timesync_disable,
> > + .read_clock = eth_ice_read_clock,
>
> I suggest following the naming convention of the rest of the ops here. ice_read_clock instead of eth_ice_read_clock.
> Check the indentation when you are reworking this. It looks like tabs were used instead of spaces ahead of the "=".
>
> > .tm_ops_get = ice_tm_ops_get,
> > .fec_get_capability = ice_fec_get_capability,
> > .fec_get = ice_fec_get,
> > @@ -6935,6 +6937,17 @@ ice_timesync_disable(struct rte_eth_dev *dev)
> > return 0;
> > }
> >
> > +static int
> > +eth_ice_read_clock(__rte_unused struct rte_eth_dev *dev, uint64_t *clock)
> > +{
> > + struct timespec system_time;
> > +
> > + clock_gettime(CLOCK_REALTIME, &system_time);
> > + *clock = system_time.tv_sec * NSEC_PER_SEC + system_time.tv_nsec;
> > +
> > + return 0;
> > +}
> > +
It's not clear to me why this patch needs to be in the set, since if an app
wants the current CPU time in nanosecond, the app can do so directly rather
than getting it from the NIC.
Also, is CLOCK_REALTIME the correct clock to be querying here. I would
think that CLOCK_MONOTONIC_RAW is a better choice to use, since it's
unaffected by system time changes.
/Bruce
next prev parent reply other threads:[~2025-06-12 15:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 21:19 [PATCH v1 0/6] Add TxPP Support for E830 Soumyadeep Hore
2025-06-06 21:19 ` [PATCH v1 1/6] net/intel: update E830 Tx Time Queue Context Structure Soumyadeep Hore
2025-06-07 17:08 ` [PATCH v2 0/6] Add TxPP Support for E830 Soumyadeep Hore
2025-06-07 17:08 ` [PATCH v2 1/6] net/intel: update E830 Tx Time Queue Context Structure Soumyadeep Hore
2025-06-07 17:09 ` [PATCH v2 2/6] net/intel: add read clock feature in ICE Soumyadeep Hore
2025-06-07 17:09 ` [PATCH v2 3/6] net/intel: add TxPP Support for E830 Soumyadeep Hore
2025-06-07 17:09 ` [PATCH v2 4/6] net/intel: add AVX2 Support for TxPP Soumyadeep Hore
2025-06-07 17:09 ` [PATCH v2 5/6] net/intel: add AVX512 " Soumyadeep Hore
2025-06-07 17:09 ` [PATCH v2 6/6] doc: announce TxPP support for E830 adapters Soumyadeep Hore
2025-06-08 11:32 ` [PATCH v3 0/6] Add TxPP Support for E830 Soumyadeep Hore
2025-06-08 11:32 ` [PATCH v3 1/6] net/intel: update E830 Tx Time Queue Context Structure Soumyadeep Hore
2025-06-08 11:32 ` [PATCH v3 2/6] net/intel: add read clock feature in ICE Soumyadeep Hore
2025-06-09 13:57 ` Bruce Richardson
2025-06-10 11:50 ` Hore, Soumyadeep
2025-06-08 11:32 ` [PATCH v3 3/6] net/intel: add TxPP Support for E830 Soumyadeep Hore
2025-06-09 12:52 ` Bruce Richardson
2025-06-10 11:47 ` Hore, Soumyadeep
2025-06-09 14:39 ` Bruce Richardson
2025-06-10 11:53 ` Hore, Soumyadeep
2025-06-08 11:32 ` [PATCH v3 4/6] net/intel: add AVX2 Support for TxPP Soumyadeep Hore
2025-06-09 15:19 ` Bruce Richardson
2025-06-08 11:32 ` [PATCH v3 5/6] net/intel: add AVX512 " Soumyadeep Hore
2025-06-09 15:21 ` Bruce Richardson
2025-06-08 11:32 ` [PATCH v3 6/6] doc: announce TxPP support for E830 adapters Soumyadeep Hore
2025-06-09 13:38 ` Bruce Richardson
2025-06-10 13:11 ` [PATCH v4 0/6] Add TxPP Support for E830 Soumyadeep Hore
2025-06-10 13:11 ` [PATCH v4 1/6] net/intel: update E830 Tx Time Queue Context Structure Soumyadeep Hore
2025-06-10 13:11 ` [PATCH v4 2/6] net/intel: add read clock feature in ICE Soumyadeep Hore
2025-06-12 10:14 ` Loftus, Ciara
2025-06-12 15:48 ` Bruce Richardson [this message]
2025-06-10 13:11 ` [PATCH v4 3/6] net/intel: add TxPP Support for E830 Soumyadeep Hore
2025-06-12 10:31 ` Loftus, Ciara
2025-06-12 16:44 ` Bruce Richardson
2025-06-10 13:11 ` [PATCH v4 4/6] net/intel: add AVX2 Support for TxPP Soumyadeep Hore
2025-06-10 13:11 ` [PATCH v4 5/6] net/intel: add AVX512 " Soumyadeep Hore
2025-06-10 13:11 ` [PATCH v4 6/6] doc: announce TxPP support for E830 adapters Soumyadeep Hore
2025-06-12 16:46 ` Bruce Richardson
2025-06-06 21:19 ` [PATCH v1 2/6] net/intel: add read clock feature in ICE Soumyadeep Hore
2025-06-06 21:19 ` [PATCH v1 3/6] net/intel: add TxPP Support for E830 Soumyadeep Hore
2025-06-06 21:19 ` [PATCH v1 4/6] net/intel: add AVX2 Support for TxPP Soumyadeep Hore
2025-06-06 21:19 ` [PATCH v1 5/6] net/intel: add AVX512 " Soumyadeep Hore
2025-06-06 21:19 ` [PATCH v1 6/6] doc: announce TxPP support for E830 adapters Soumyadeep Hore
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=aEr202MXrf3Mnsm-@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=manoj.kumar.subbarao@intel.com \
--cc=soumyadeep.hore@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 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).