From: Bruce Richardson <bruce.richardson@intel.com>
To: Soumyadeep Hore <soumyadeep.hore@intel.com>
Cc: <dev@dpdk.org>, <aman.deep.singh@intel.com>,
<rajesh3.kumar@intel.com>, <manoj.kumar.subbarao@intel.com>
Subject: Re: [PATCH v3 3/4] net/intel: add support for Precision Time Protocol
Date: Tue, 16 Dec 2025 12:43:12 +0000 [thread overview]
Message-ID: <aUFT4BwL-wYqSof_@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251103160646.140084-4-soumyadeep.hore@intel.com>
On Mon, Nov 03, 2025 at 11:06:44AM -0500, Soumyadeep Hore wrote:
> Add support for PTP that contains negotiation with CP to receive a
> set of supported functionalities through capabilities,
> get/set/adjust the time of the main timer and Tx timestamping
> through secondary mailbox dedicated to PTP.
>
> Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
> ---
> drivers/net/intel/common/tx.h | 1 +
> drivers/net/intel/idpf/idpf_common_rxtx.c | 186 +++++++++------
> drivers/net/intel/idpf/idpf_common_rxtx.h | 10 +
> drivers/net/intel/idpf/idpf_ethdev.c | 275 ++++++++++++++++++++++
> 4 files changed, 401 insertions(+), 71 deletions(-)
>
> diff --git a/drivers/net/intel/common/tx.h b/drivers/net/intel/common/tx.h
> index 5af64a4cfe..fe175f7d65 100644
> --- a/drivers/net/intel/common/tx.h
> +++ b/drivers/net/intel/common/tx.h
> @@ -113,6 +113,7 @@ struct ci_tx_queue {
> uint16_t sw_tail;
> uint16_t rs_compl_count;
> uint8_t expected_gen_id;
> + uint32_t latch_idx; /* Tx timestamp latch index */
This creates padding in the structure. Unless there is a good reason why
not, generally structure variables should be kept in order of size, from
biggest to smallest to avoid padding.
/Bruce
next prev parent reply other threads:[~2025-12-16 12:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 12:08 [PATCH v1 0/4] Enable PTP feature for MEV Soumyadeep Hore
2025-10-24 12:08 ` [PATCH v1 1/4] net/idpf: add a new API for PTP support Soumyadeep Hore
2025-10-24 12:08 ` [PATCH v1 2/4] net/idpf: add PTP virtchnl2 support Soumyadeep Hore
2025-10-24 12:08 ` [PATCH v1 3/4] net/intel: add support for Precision Time Protocol Soumyadeep Hore
2025-10-24 12:08 ` [PATCH v1 4/4] doc: add PTP IDPF documentation Soumyadeep Hore
2025-10-24 16:28 ` Stephen Hemminger
2025-10-28 6:07 ` [PATCH v2 0/4] Enable PTP feature for MEV Soumyadeep Hore
2025-10-28 6:07 ` [PATCH v2 1/4] net/idpf: add a new API for PTP support Soumyadeep Hore
2025-10-28 6:07 ` [PATCH v2 2/4] net/idpf: add PTP virtchnl2 support Soumyadeep Hore
2025-10-28 6:07 ` [PATCH v2 3/4] net/intel: add support for Precision Time Protocol Soumyadeep Hore
2025-10-28 6:07 ` [PATCH v2 4/4] doc: add PTP IDPF documentation Soumyadeep Hore
2025-10-30 9:41 ` Bruce Richardson
2025-11-03 16:06 ` [PATCH v3 0/4] Enable PTP feature for MEV Soumyadeep Hore
2025-11-03 16:06 ` [PATCH v3 1/4] net/idpf: add a new API for PTP support Soumyadeep Hore
2025-11-03 16:06 ` [PATCH v3 2/4] net/idpf: add PTP virtchnl2 support Soumyadeep Hore
2025-11-03 16:06 ` [PATCH v3 3/4] net/intel: add support for Precision Time Protocol Soumyadeep Hore
2025-12-16 12:43 ` Bruce Richardson [this message]
2025-11-03 16:06 ` [PATCH v3 4/4] doc: add PTP IDPF documentation 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=aUFT4BwL-wYqSof_@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=manoj.kumar.subbarao@intel.com \
--cc=rajesh3.kumar@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).