From: Thomas Monjalon <thomas@monjalon.net>
To: "Tomasz Duszynski" <tduszynski@marvell.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Cc: jerinj@marvell.com, bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: [PATCH v2 6/6] trace: add PMU
Date: Wed, 18 Jun 2025 11:47:13 +0200 [thread overview]
Message-ID: <3793563.K4a6FZZPjd@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FD08@smartserver.smartshare.dk>
18/06/2025 09:16, Morten Brørup:
> > diff --git a/lib/meson.build b/lib/meson.build
> > index 1934cb4a29..87b567f01b 100644
> > --- a/lib/meson.build
> > +++ b/lib/meson.build
> > @@ -13,7 +13,7 @@ libraries = [
> > 'kvargs', # eal depends on kvargs
> > 'argparse',
> > 'telemetry', # basic info querying
> > - 'pmu',
> > + 'pmu', # trace depends on pmu
> > 'eal', # everything depends on eal
> > 'ptr_compress',
> > 'ring',
>
> @Tomasz,
>
> Please re-read my v1 review feedback [1]:
> The PMU library should depend on the EAL, not the other way around!
It should depend on the low-level EAL, yes.
But as of now, EAL is not split so it is better to avoid EAL dependency if possible.
> How else is the PMU library supposed to use EAL functions like rte_mem_page_size()?
>
> @Jerin or @Bruce, do any of you have some suggestions for how to achieve the proper dependency chain here?
I propose we don't use rte_mem_page_size() in PMU lib for now,
so we keep not depending on EAL, to avoid mixing all in future.
Later we could fix it if we manage to have high level EAL as a separate library.
> Worst case, we will have to move PMU into EAL. :-(
>
> [1]: https://inbox.dpdk.org/dev/98CBD80474FA8B44BF855DF32C47DC35E9FCFA@smartserver.smartshare.dk/T/#u
>
> Besides that, good stuff. :-)
next prev parent reply other threads:[~2025-06-18 9:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 6:53 [PATCH 0/6] lib/pmu: cleanups and trace integration Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 1/6] lib/pmu: quiesce rte_pmu_read deprecation warning in chkincs Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 2/6] lib/pmu: export only necessary arch headers Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 3/6] lib/pmu: reimplement per-arch ops as callbacks Tomasz Duszynski
2025-06-16 7:03 ` Thomas Monjalon
2025-06-16 9:54 ` Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 4/6] lib/pmu: use build system defined RTE_LIB_PMU macro Tomasz Duszynski
2025-06-16 7:08 ` Thomas Monjalon
2025-06-16 10:53 ` Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 5/6] test/pmu: enable fast test Tomasz Duszynski
2025-06-16 6:53 ` [PATCH 6/6] trace: add PMU Tomasz Duszynski
2025-06-16 7:13 ` Thomas Monjalon
2025-06-16 9:49 ` Tomasz Duszynski
2025-06-16 10:32 ` Bruce Richardson
2025-06-16 13:18 ` Morten Brørup
2025-06-18 6:56 ` [PATCH v2 0/6] lib/pmu: cleanups and trace integration Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 1/6] lib/pmu: quiesce rte_pmu_read deprecation warning in chkincs Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 2/6] lib/pmu: export only necessary arch headers Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 3/6] lib/pmu: reimplement per-arch ops as callbacks Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 4/6] lib/pmu: use build system defined RTE_LIB_PMU macro Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 5/6] test/pmu: enable fast test Tomasz Duszynski
2025-06-18 6:56 ` [PATCH v2 6/6] trace: add PMU Tomasz Duszynski
2025-06-18 7:16 ` Morten Brørup
2025-06-18 9:47 ` Thomas Monjalon [this message]
2025-06-18 10:28 ` Bruce Richardson
2025-06-18 11:30 ` Morten Brørup
2025-06-18 10:23 ` Tomasz Duszynski
2025-06-18 10:37 ` Morten Brørup
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=3793563.K4a6FZZPjd@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=tduszynski@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 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).