From: David Marchand <david.marchand@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v9] eal: add build-time option to omit trace
Date: Tue, 8 Oct 2024 12:15:26 +0200 [thread overview]
Message-ID: <CAJFAV8wGK7j2rTM48J4GqS2m3n07fHErA7uMpA99Y=crEBmeBw@mail.gmail.com> (raw)
In-Reply-To: <20241007114601.2921507-1-mb@smartsharesystems.com>
On Mon, Oct 7, 2024 at 1:46 PM Morten Brørup <mb@smartsharesystems.com> wrote:
>
> Some applications want to omit the trace feature.
> Either to reduce the memory footprint, to reduce the exposed attack
> surface, or for other reasons.
>
> This patch adds an option in rte_config.h to include or omit trace in the
> build. Trace is included by default.
>
> Omitting trace works by omitting all trace points.
> For API and ABI compatibility, the trace feature itself remains.
>
> Furthermore, a public function to determine if trace is build time enabled
> is added; mainly for the benefit of the dpdk-test application.
>
> Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Series applied.
Thanks Morten.
--
David Marchand
prev parent reply other threads:[~2024-10-08 10:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:55 [PATCH] " Morten Brørup
2024-09-18 9:49 ` Jerin Jacob
2024-09-18 10:23 ` Morten Brørup
2024-09-19 8:06 ` [PATCH v2] " Morten Brørup
2024-09-19 8:51 ` Jerin Jacob
2024-09-19 13:15 ` Morten Brørup
2024-09-19 13:54 ` Jerin Jacob
2024-09-19 15:35 ` Morten Brørup
2024-09-19 15:49 ` Jerin Jacob
2024-09-19 16:08 ` Morten Brørup
2024-09-19 16:34 ` Jerin Jacob
2024-09-20 9:08 ` [PATCH v3] " Morten Brørup
2024-09-23 8:39 ` Jerin Jacob
2024-09-24 13:50 ` Morten Brørup
2024-09-24 13:39 ` [PATCH v4] " Morten Brørup
2024-09-24 15:30 ` Stephen Hemminger
2024-09-24 15:41 ` Jerin Jacob
2024-09-24 15:53 ` Morten Brørup
2024-09-24 15:57 ` Jerin Jacob
2024-10-01 13:49 ` Morten Brørup
2024-10-01 14:05 ` Jerin Jacob
2024-10-01 14:14 ` Morten Brørup
2024-10-01 15:01 ` Jerin Jacob
2024-10-01 16:01 ` Morten Brørup
2024-10-01 16:06 ` Jerin Jacob
2024-10-01 16:15 ` Morten Brørup
2024-10-02 16:17 ` Jerin Jacob
2024-10-06 12:58 ` Morten Brørup
2024-10-06 12:38 ` [PATCH v5] " Morten Brørup
2024-10-06 13:58 ` [PATCH v6] " Morten Brørup
2024-10-07 5:45 ` Jerin Jacob
2024-10-07 6:07 ` Morten Brørup
2024-10-06 14:03 ` [PATCH v7] " Morten Brørup
2024-10-06 14:09 ` Morten Brørup
2024-10-07 11:46 ` [PATCH v9] " Morten Brørup
2024-10-08 7:16 ` Morten Brørup
2024-10-08 10:15 ` David Marchand [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='CAJFAV8wGK7j2rTM48J4GqS2m3n07fHErA7uMpA99Y=crEBmeBw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=skori@marvell.com \
--cc=stephen@networkplumber.org \
/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).