From: "David Harton (dharton)" <dharton@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Eliminate config/rte_config.h?
Date: Thu, 12 Nov 2020 15:39:10 +0000 [thread overview]
Message-ID: <MN2PR11MB3886EF3C3970F2E9C79CD1EDAAE70@MN2PR11MB3886.namprd11.prod.outlook.com> (raw)
Hi folks,
Been experimenting with DPDK 20.11 and the loss of the old "config" hierarchy.
I wonder if anyone considered eliminating config/rte_config.h in favor of a config/dpdk_conf that can contain the default values at the start of the file but can be overridden with values later in the file similar to how the old config files worked?
It just feels awkward to modify a versioned header file per build especially if multiple builds want to share the same repo but with different values specified in config/rte_config.h especially when "rte_build_config.h" is included at the very beginning of config/rte_config.h.
Thoughts?
Dave
next reply other threads:[~2020-11-12 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 15:39 David Harton (dharton) [this message]
2020-11-12 15:48 ` Bruce Richardson
2020-11-12 16:33 ` Bruce Richardson
2020-11-12 17:09 ` David Harton (dharton)
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=MN2PR11MB3886EF3C3970F2E9C79CD1EDAAE70@MN2PR11MB3886.namprd11.prod.outlook.com \
--to=dharton@cisco.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 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).