From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>,
"David Marchand" <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>,
<frode.nordahl@canonical.com>, <mattias.ronnblom@ericsson.com>
Subject: Re: [PATCH 0/3] Defer lcore variables allocation
Date: Mon, 16 Dec 2024 11:01:22 +0100 [thread overview]
Message-ID: <7b5c81e8-0e64-4024-a068-f9788ec5bd5e@intel.com> (raw)
In-Reply-To: <64f3a221-8692-4c4a-ae59-8e97a93dbf03@lysator.liu.se>
On 12/10/2024 10:41 AM, Mattias Rönnblom wrote:
<snip>
>
> Maybe the DAG is available on the build (meson) level, and thus the code
> can be generated out of that?
There is in fact a patchset that produces just that kind of graph:
https://patches.dpdk.org/project/dpdk/list/?series=34055
It's currently not very consumable by DPDK and it'd be a difficult task
to integrate it into DPDK in such a way as to allow arbitrary libraries
to use it, but building such a graph from build system is doable.
However, IMO it would be easier to build such a graph at init time,
where a component would register its dependencies with EAL, and EAL
would handle the rest. That way, the bulk of the work lands in EAL,
while component developers only have to specify the things they depend
on. It could be a little tricky in that some components may depend on
e.g. IPC which isn't a "component" as much as it's an init stage, but
depending on IPC could just as well be depending on EAL having done
init, while for internal components we can come up with some sort of
internal init order mechanism.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2024-12-16 10:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 17:57 David Marchand
2024-12-05 17:57 ` [PATCH 1/3] random: defer seeding to EAL init David Marchand
2024-12-06 11:09 ` Mattias Rönnblom
2024-12-16 9:38 ` Burakov, Anatoly
2024-12-05 17:57 ` [PATCH 2/3] power: defer lcore variable allocation David Marchand
2024-12-06 11:29 ` Mattias Rönnblom
2024-12-12 7:57 ` David Marchand
2024-12-13 6:58 ` Mattias Rönnblom
2024-12-16 10:02 ` David Marchand
2024-12-05 17:57 ` [PATCH 3/3] eal/x86: defer power intrinsics " David Marchand
2024-12-06 11:32 ` Mattias Rönnblom
2024-12-06 11:01 ` [PATCH 0/3] Defer lcore variables allocation Mattias Rönnblom
2024-12-06 15:55 ` Thomas Monjalon
2024-12-10 17:09 ` Stephen Hemminger
2024-12-09 11:03 ` David Marchand
2024-12-09 15:39 ` Mattias Rönnblom
2024-12-09 17:40 ` David Marchand
2024-12-10 9:41 ` Mattias Rönnblom
2024-12-16 10:01 ` Burakov, Anatoly [this message]
2024-12-16 9:42 ` Burakov, Anatoly
2024-12-16 9:49 ` David Marchand
2024-12-17 9:06 ` David Marchand
2024-12-18 20:10 ` Mattias Rönnblom
2024-12-17 8:59 ` [PATCH v2 0/5] " David Marchand
2024-12-17 8:59 ` [PATCH v2 1/5] eal: check lcore variable handle David Marchand
2024-12-18 11:18 ` Burakov, Anatoly
2024-12-17 8:59 ` [PATCH v2 2/5] random: defer seeding to EAL init David Marchand
2024-12-18 16:35 ` Stephen Hemminger
2024-12-18 17:03 ` Mattias Rönnblom
2024-12-17 8:59 ` [PATCH v2 3/5] power: defer lcore variable allocation David Marchand
2024-12-18 11:17 ` Burakov, Anatoly
2024-12-17 8:59 ` [PATCH v2 4/5] power: reduce memory footprint of per-lcore state David Marchand
2024-12-18 11:17 ` Burakov, Anatoly
2024-12-17 8:59 ` [PATCH v2 5/5] eal/x86: defer power intrinsics variable allocation David Marchand
2024-12-18 11:17 ` Burakov, Anatoly
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=7b5c81e8-0e64-4024-a068-f9788ec5bd5e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=frode.nordahl@canonical.com \
--cc=hofors@lysator.liu.se \
--cc=mattias.ronnblom@ericsson.com \
--cc=thomas@monjalon.net \
/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).