From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Sivaprasad Tummala" <sivaprasad.tummala@amd.com>,
jerinj@marvell.com, dev@dpdk.org
Subject: Re: [PATCH] eventdev: fix alignment padding
Date: Tue, 8 Aug 2023 15:54:27 +0530 [thread overview]
Message-ID: <CALBAE1Ou6_fFfHfU_ARriN6jSAzPLLCOUdRwUcPf3q0Z+Pv_GA@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1MBJxzGAC1BjDi6D+UWfzjdwHaX2S=RYrKmeasy5ktObQ@mail.gmail.com>
On Wed, Aug 2, 2023 at 9:49 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> On Tue, May 23, 2023 at 8:45 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
> >
> > On Wed, May 17, 2023 at 7:05 PM Morten Brørup <mb@smartsharesystems.com> wrote:
> > >
>
> > Shiva,
> >
> > Please send ABI change notice for this for 23.11 NOW.
> > Once it is Acked and merged. I will merge the patch for 23.11 release.
> >
> > I am marking the patch as DEFERRED in patchwork and next release
> > window it will come as NEW in patchwork.
>
>
> Any objection to merge this?
pahole output after the change,
[for-main]dell[dpdk-next-eventdev] $ pahole build/app/test/dpdk-test
-C rte_event_fp_ops
struct rte_event_fp_ops {
void * * data; /* 0 8 */
event_enqueue_t enqueue; /* 8 8 */
event_enqueue_burst_t enqueue_burst; /* 16 8 */
event_enqueue_burst_t enqueue_new_burst; /* 24 8 */
event_enqueue_burst_t enqueue_forward_burst; /* 32 8 */
event_dequeue_t dequeue; /* 40 8 */
event_dequeue_burst_t dequeue_burst; /* 48 8 */
event_maintain_t maintain; /* 56 8 */
/* --- cacheline 1 boundary (64 bytes) --- */
event_tx_adapter_enqueue_t txa_enqueue; /* 64 8 */
event_tx_adapter_enqueue_t txa_enqueue_same_dest; /* 72 8 */
event_crypto_adapter_enqueue_t ca_enqueue; /* 80 8 */
uintptr_t reserved[5]; /* 88 40 */
/* size: 128, cachelines: 2, members: 12 */
} __attribute__((__aligned__(64)));
Acked-by: Jerin Jacob <jerinj@marvell.com>
next prev parent reply other threads:[~2023-08-08 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 10:45 Sivaprasad Tummala
2023-04-18 11:06 ` Morten Brørup
2023-04-18 12:40 ` Mattias Rönnblom
2023-04-18 12:30 ` Mattias Rönnblom
2023-04-18 14:07 ` Morten Brørup
2023-04-18 15:16 ` Mattias Rönnblom
2023-04-19 6:38 ` Morten Brørup
2023-05-17 13:20 ` Jerin Jacob
2023-05-17 13:35 ` Morten Brørup
2023-05-23 15:15 ` Jerin Jacob
2023-08-02 16:19 ` Jerin Jacob
2023-08-08 10:24 ` Jerin Jacob [this message]
2023-08-08 10:25 ` 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=CALBAE1Ou6_fFfHfU_ARriN6jSAzPLLCOUdRwUcPf3q0Z+Pv_GA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mb@smartsharesystems.com \
--cc=sivaprasad.tummala@amd.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).