DPDK patches and discussions
 help / color / mirror / Atom feed
From: Soumyadeep Hore <soumyadeep.hore@intel.com>
To: bruce.richardson@intel.com, aman.deep.singh@intel.com
Cc: dev@dpdk.org, Paul Greenwalt <paul.greenwalt@intel.com>
Subject: [PATCH v1 1/2] net/ice: add tstamp descriptor
Date: Fri, 17 Jan 2025 09:39:37 +0000	[thread overview]
Message-ID: <20250117093938.1184042-2-soumyadeep.hore@intel.com> (raw)
In-Reply-To: <20250117093938.1184042-1-soumyadeep.hore@intel.com>

From: Paul Greenwalt <paul.greenwalt@intel.com>

The Tx packet pacing (TXPP) tstamp queue descriptor is a 32bit format.
- Tx queue descriptor ring index, bits 12:0
- Time Stamp, bits 31:13

Add struct ice_ts_desc to hold the 32bit descriptor.

Signed-off-by: Paul Greenwalt <paul.greenwalt@intel.com>
Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
---
 drivers/net/ice/base/ice_lan_tx_rx.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/net/ice/base/ice_lan_tx_rx.h b/drivers/net/ice/base/ice_lan_tx_rx.h
index 209b8e5c43..bcc6e9a716 100644
--- a/drivers/net/ice/base/ice_lan_tx_rx.h
+++ b/drivers/net/ice/base/ice_lan_tx_rx.h
@@ -1269,6 +1269,12 @@ struct ice_tx_drbell_q_ctx {
 };
 #pragma pack()
 
+/* Tx time stamp descriptor */
+struct ice_ts_desc {
+	__le32 tx_desc_idx_tstamp;
+};
+#define ICE_TS_DESC(R, i) (&(((struct ice_ts_desc *)((R)->desc))[i]))
+
 /* The ice_ptype_lkup table is used to convert from the 10-bit ptype in the
  * hardware to a bit-field that can be used by SW to more easily determine the
  * packet type.
-- 
2.43.0


  reply	other threads:[~2025-01-17 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17  9:39 [PATCH v1 0/2] Update Base code for TXPP Implementation Soumyadeep Hore
2025-01-17  9:39 ` Soumyadeep Hore [this message]
2025-01-17  9:39 ` [PATCH v1 2/2] net/ice: add Tx Time queue context configuration support 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=20250117093938.1184042-2-soumyadeep.hore@intel.com \
    --to=soumyadeep.hore@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=paul.greenwalt@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).