From: Thomas Monjalon <thomas@monjalon.net>
To: David Christensen <drc@linux.ibm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Sunil Kumar Kori <skori@marvell.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [EXTERNAL] [PATCH] trace: force 8 byte alignment when --no-huge is used
Date: Wed, 24 Sep 2025 16:54:29 +0200 [thread overview]
Message-ID: <16437299.JCcGWNJJiE@thomas> (raw)
In-Reply-To: <BY3PR18MB47852312E4B66F4EC22851DCC85EA@BY3PR18MB4785.namprd18.prod.outlook.com>
24/07/2025 13:05, Jerin Jacob:
> From: David Christensen <drc@linux.ibm.com>
> >
> > Current code in eal_trace_init() specifies 8 byte alignment for CTF generation,
> > but fallback code in __rte_trace_mem_per_thread() does not enforce similar
> > requirements when calling malloc(). Modify fallback heap requests to use
> > posix_memalign()
> > Current code in eal_trace_init() specifies 8 byte alignment for CTF generation,
> > but fallback code in __rte_trace_mem_per_thread() does not enforce similar
> > requirements when calling malloc(). Modify fallback heap requests to use
> > posix_memalign() with proper alignment.
> >
> > Signed-off-by: David Christensen <drc@linux.ibm.com>
>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
>
> > Bugzilla-ID: 1715
Applied, thanks.
Note: seems unrelated to --no-huge, so dropped from the title.
prev parent reply other threads:[~2025-09-24 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 0:05 [PATCH] trace: force 8 byte alignment when --no-huge is used David Christensen
2025-07-24 11:05 ` [EXTERNAL] " Jerin Jacob
2025-09-24 14:54 ` Thomas Monjalon [this message]
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=16437299.JCcGWNJJiE@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=jerinj@marvell.com \
--cc=roretzla@linux.microsoft.com \
--cc=skori@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.