From: Doug Goldstein <cardoe@cardoe.com>
To: Jan Beulich <JBeulich@suse.com>,
Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
lars.kurth.xen@gmail.com,
Dario Faggioli <dario.faggioli@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 2/5] build: Hook the schedulers into Kconfig
Date: Mon, 11 Jan 2016 11:17:20 -0600 [thread overview]
Message-ID: <5693E3A0.4030200@cardoe.com> (raw)
In-Reply-To: <5693EB2A02000078000C592F@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
On 1/11/16 10:49 AM, Jan Beulich wrote:
>>>> On 11.01.16 at 17:31, <cardoe@cardoe.com> wrote:
>> There have been a good deal number of different downstreams that have
>> been encouraging of changes like this but it seems like you are
>> fundamentally opposed. Which is plainly discouraging to people to
>> attempt to engage upstream.
>
> I could see such a reaction as being valid if I objected to any of
> the configurability changes, but I have a hard time following when
> I just ask for the default scheduler to not become configurable.
> Plus I'm not the only one involved in getting to a decision here, i.e.
> I can easily be overruled by other maintainers.
>
I really hate to use Linux as an example here since its a different
project but I will anyway. Linux has a number of flags like this were
you can remove the default. The compression algorithm, the CPU schedule,
the I/O scheduler. So it doesn't seem that far fetched to allow that.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-11 17:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 21:22 [PATCH v4 0/5] Allow schedulers to be selectable through Kconfig Jonathan Creekmore
2016-01-08 21:22 ` [PATCH v4 1/5] build: Env var to enable expert config options Jonathan Creekmore
2016-01-08 21:22 ` [PATCH v4 2/5] build: Hook the schedulers into Kconfig Jonathan Creekmore
2016-01-09 14:52 ` Andrew Cooper
2016-01-09 17:50 ` Jonathan Creekmore
2016-01-09 18:08 ` Andrew Cooper
2016-01-09 22:47 ` Jonathan Creekmore
2016-01-11 13:59 ` Jan Beulich
2016-01-11 14:07 ` Jan Beulich
2016-01-11 15:10 ` Jonathan Creekmore
2016-01-11 15:43 ` Jan Beulich
2016-01-11 16:31 ` Doug Goldstein
2016-01-11 16:49 ` Jan Beulich
2016-01-11 17:17 ` Doug Goldstein [this message]
2016-01-08 21:22 ` [PATCH v4 3/5] build: Alloc space for sched list in the link file Jonathan Creekmore
2016-01-09 18:25 ` Andrew Cooper
2016-01-09 22:46 ` Jonathan Creekmore
2016-01-08 21:22 ` [PATCH v4 4/5] sched: Register the schedulers into the list Jonathan Creekmore
2016-01-08 21:22 ` [PATCH v4 5/5] sched: Use the auto-generated list of schedulers Jonathan Creekmore
2016-01-09 18:28 ` Andrew Cooper
2016-01-09 22:43 ` Jonathan Creekmore
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=5693E3A0.4030200@cardoe.com \
--to=cardoe@cardoe.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jonathan.creekmore@gmail.com \
--cc=lars.kurth.xen@gmail.com \
--cc=xen-devel@lists.xenproject.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.