From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/2] config: disable CONFIG_RTE_SCHED_VECTOR for arm
Date: Mon, 30 Nov 2015 15:13:53 +0100 [thread overview]
Message-ID: <3362350.VxlxT3kjya@xps13> (raw)
In-Reply-To: <20151130150421.43d50e59@pcviktorin.fit.vutbr.cz>
2015-11-30 15:04, Jan Viktorin:
> On Mon, 30 Nov 2015 14:59:45 +0100
> Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
>
> > 2015-11-30 14:27, Jan Viktorin:
> > > I believe (and have already expressed this idea) that this is not a
> > > problem of architecture ports but it is a problem of the build system.
> > > Love me or hate me, in my opinion the build system is broken :). The
> > > build system should be able to solve this.
> > >
> > > I've created privately an integration of kconfig into DPDK, however, it
> > > is far from being usable and I did not have time to make at least an
> > > RFC patch. If there is an attitude in the community to include such
> > > thing in the future versions, I'd like to make some more effort in this
> > > area.
> >
> > If we were integrating kconfig, we should consider kconfig-frontends
> > (http://ymorin.is-a-geek.org/projects/kconfig-frontends).
>
> True, this seems to be the easiest way. I've already used it
> successfully.
>
> > But I'm not sure it is the way to go. You are welcome to open the debate
> > in a dedicated thread by explaining the benefits compared to a configuration
> > script.
>
> OK. I will consider this. Probably, after the community call... (Or
> before?)
Please take your time.
We will better ready to discuss it when the "make install" issue will be
solved.
> > I think most of the options could be automatically guessed given the target
> > CPU, kernel, libc and compiler. It looks like a scripting task, not a
> > manual configuration (as kconfig provides). But maybe we can mix kconfig
> > and some automatic defaults.
> >
>
> Well, scripting... If you have issues like "feature X" does not work
> on "platform A" then you need to express this. If you try to script
> such dependency, I am afraid you always end up with a system of the same
> or equivalent complexity as the kconfig already has :). We'll see...
I'm not speaking about complexity here, but just features.
With kconfig, options and dependencies are well described but the defaults
are fixed. With a script, you can have some dynamically generated defaults.
Please expose the needs and features clearly in another thread. Thanks
next prev parent reply other threads:[~2015-11-30 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 13:34 [dpdk-dev] [PATCH v3 0/2] " Jerin Jacob
2015-11-27 13:34 ` [dpdk-dev] [PATCH v3 1/2] config: arm64: create common arm64 configs under common_arm64 file Jerin Jacob
2015-11-27 13:34 ` [dpdk-dev] [PATCH v3 2/2] config: disable CONFIG_RTE_SCHED_VECTOR for arm Jerin Jacob
2015-11-27 14:36 ` Jan Viktorin
2015-11-29 23:48 ` Jianbo Liu
2015-11-30 5:47 ` Jerin Jacob
2015-11-30 17:03 ` Jianbo Liu
2015-11-30 10:22 ` Jerin Jacob
2015-11-30 18:55 ` Jianbo Liu
2015-11-30 13:27 ` Jan Viktorin
2015-11-30 13:59 ` Thomas Monjalon
2015-11-30 14:04 ` Jan Viktorin
2015-11-30 14:13 ` Thomas Monjalon [this message]
2015-11-27 14:40 ` [dpdk-dev] [PATCH v3 0/2] " Jan Viktorin
2015-11-27 14:49 ` Thomas Monjalon
2015-11-30 16:37 ` Stephen Hemminger
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=3362350.VxlxT3kjya@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=viktorin@rehivetech.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).