All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH 24.03 v2] build: track mandatory rather than optional libs
Date: Fri, 3 Nov 2023 18:31:30 +0100	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9EFCF@smartserver.smartshare.dk> (raw)
In-Reply-To: <20231103165208.1210182-1-bruce.richardson@intel.com>

> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Friday, 3 November 2023 17.52
> 
> DPDK now has more optional libraries than mandatory ones, so invert the
> list stored in the meson.build file from the optional ones to the
> "always_enable" ones. As well as being a shorter list:
> 
> * we can remove the loop building up the "always_enable" list
>   dynamically from the optional list
> * it better aligns with the drivers/meson.build file which maintains an
>   always_enable list.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Excellent!

It really shows how bloated DPDK CORE still is. I would like to see these go optional:

acl - OPTIONAL
cmdline - OPTIONAL (if not used by EAL)
eal - CORE
ethdev - CORE, or OPTIONAL for secondary process
fib - OPTIONAL
hash - OPTIONAL (if not used by CORE libs)
kvargs - OPTIONAL (if not used by EAL)
log - CORE
lpm - OPTIONAL
mbuf - CORE
mempool - CORE
meter - OPTIONAL
net - CORE
pci - CORE, or OPTIONAL for secondary process
rcu - OPTIONAL (if not used by CORE libs)
rib - OPTIONAL
ring - CORE
stack - OPTIONAL (if not used by CORE libs)
telemetry - OPTIONAL
timer - OPTIONAL (if not used by CORE libs)

Anyway,

Acked-by: Morten Brørup <mb@smartsharesystems.com>


  reply	other threads:[~2023-11-03 17:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 16:28 [PATCH 24.03] build: track mandatory rather than optional libs Bruce Richardson
2023-11-03 16:52 ` [PATCH 24.03 v2] " Bruce Richardson
2023-11-03 17:31   ` Morten Brørup [this message]
2023-11-03 18:08     ` Bruce Richardson
2023-11-03 20:19       ` Morten Brørup
2023-11-06 10:28         ` Bruce Richardson
2023-11-06 11:22           ` Morten Brørup
2023-11-06 11:27             ` Bruce Richardson
2023-11-06 11:37               ` Morten Brørup
2023-12-20 14:21 ` [PATCH v3 0/3] Improve optional lib support Bruce Richardson
2023-12-20 14:21   ` [PATCH v3 1/3] build: track mandatory rather than optional libs Bruce Richardson
2023-12-20 14:21   ` [PATCH v3 2/3] build: remove 5 libs from mandatory list Bruce Richardson
2023-12-20 15:18     ` Morten Brørup
2023-12-20 16:05       ` Bruce Richardson
2023-12-20 14:21   ` [PATCH v3 3/3] build: RFC - add support for optional dependencies Bruce Richardson
2023-12-20 15:08     ` Morten Brørup
2023-12-20 15:43       ` Bruce Richardson
2024-10-04 20:59         ` Stephen Hemminger
2024-02-01  9:23   ` [PATCH v3 0/3] Improve optional lib support David Marchand
2024-02-01  9:25     ` Bruce Richardson

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=98CBD80474FA8B44BF855DF32C47DC35E9EFCF@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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 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.