DPDK patches and discussions
 help / color / mirror / Atom feed
From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Ray Kinsella <mdr@ashroe.eu>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [PATCH 2/3] eventdev: replace *u64s with u64s in event vector
Date: Thu, 29 Sep 2022 15:27:47 +0530	[thread overview]
Message-ID: <20220929095748.12563-2-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20220929095748.12563-1-pbhagavatula@marvell.com>

From: Pavan Nikhilesh <pbhagavatula@marvell.com>

Replace *u64s with u64s in rte_event_vector structure as
the *ptrs already serves the purpose of holding pointers
and the intention of u64s is to hold array of uint64_t
values.

Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
 doc/guides/rel_notes/deprecation.rst | 3 ---
 lib/eventdev/rte_eventdev.h          | 2 +-
 2 files changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 2826a38f03..bb44b1f9ff 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -173,9 +173,6 @@ Deprecation Notices
   Event will be one of the configuration fields,
   together with additional vector parameters.
 
-* eventdev: The element ``*u64s`` in the structure ``rte_event_vector``
-  is deprecated and will be replaced with ``u64s`` in DPDK 22.11.
-
 * eventdev: The structure ``rte_event_vector`` will be modified to include
   ``elem_offset:12`` bits taken from ``rsvd:15``. The ``elem_offset`` defines
   the offset into the vector array from which valid elements are present.
diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h
index 86d656a08b..1cbeb6bddc 100644
--- a/lib/eventdev/rte_eventdev.h
+++ b/lib/eventdev/rte_eventdev.h
@@ -1117,7 +1117,7 @@ struct rte_event_vector {
 #endif
 		struct rte_mbuf *mbufs[0];
 		void *ptrs[0];
-		uint64_t *u64s[0];
+		uint64_t u64s[0];
 #ifndef __cplusplus
 	} __rte_aligned(16);
 #endif
-- 
2.25.1


  reply	other threads:[~2022-09-29 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  9:57 [PATCH 1/3] eventdev: add rte prefix to function declaration pbhagavatula
2022-09-29  9:57 ` pbhagavatula [this message]
2022-09-29  9:57 ` [PATCH 3/3] doc: remove deprecation notices for event vector pbhagavatula
2022-09-30 10:16   ` Jerin Jacob

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=20220929095748.12563-2-pbhagavatula@marvell.com \
    --to=pbhagavatula@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mdr@ashroe.eu \
    /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).