From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Goldstein Subject: Re: [PATCH v4 2/5] build: Hook the schedulers into Kconfig Date: Mon, 11 Jan 2016 11:17:20 -0600 Message-ID: <5693E3A0.4030200@cardoe.com> References: <1452288166-43501-1-git-send-email-jonathan.creekmore@gmail.com> <1452288166-43501-3-git-send-email-jonathan.creekmore@gmail.com> <5693C52602000078000C56EF@prv-mh.provo.novell.com> <5693DBA702000078000C5851@prv-mh.provo.novell.com> <5693D8EF.4080002@cardoe.com> <5693EB2A02000078000C592F@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6413334223097334767==" Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aIg5v-0006u1-28 for xen-devel@lists.xenproject.org; Mon, 11 Jan 2016 17:17:27 +0000 Received: by mail-yk0-f195.google.com with SMTP id v14so27055894ykd.1 for ; Mon, 11 Jan 2016 09:17:25 -0800 (PST) In-Reply-To: <5693EB2A02000078000C592F@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Jonathan Creekmore Cc: George Dunlap , lars.kurth.xen@gmail.com, Dario Faggioli , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============6413334223097334767== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ADPimQnBB8pjfrw1tecVUfeeoBuxdW219" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ADPimQnBB8pjfrw1tecVUfeeoBuxdW219 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 1/11/16 10:49 AM, Jan Beulich wrote: >>>> On 11.01.16 at 17:31, 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. >=20 > 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. >=20 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. --=20 Doug Goldstein --ADPimQnBB8pjfrw1tecVUfeeoBuxdW219 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0 iQJ8BAEBCgBmBQJWk+OhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNTM5MEQ2RTNFMTkyNzlCNzVDMzIwOTVB MkJDMDNEQzg3RUQxQkQ0AAoJEKK8A9yH7RvUoHYP/3mvd8tAsNzUVKH1GAwLfufA BpYJX2KofOSdtxg0RAiNeqqrwLfraYW/RKxEJjRGzm1GQffEPP1ZiG8/Rx2ZWo59 DXAi/UYgALW9dwBjiT2UagyHRolHZp8y+hlH3WPh+buAIG4bOw1VTbHRM39nrl8E sRJinYhxGJWNCsfnhwheanNZed3dEtmPWjTLHYESB3HG8PqsRb9Irke8qHclZaNp L9RSGIV1fdajCG+3wjXMhNe9mxjupVvPODcs4Yl4sdySZN9ul3Uwov38i19K20rM Jmk0AimEmf/T6YF3nk7lz56lpRefDb3mWuqLzYY56ua5cRWEmibw6VLtkZv1Zw24 vZ7Fxgckq9M9cDAPUViHjAPd2c6H+A3A6x4arzc3mWcotCP5Ac5mAFTp2xch02W+ WzFbxDfTS0Gfn90vspDZxGAHo/Ehl6OVpPwfwUY1j1hNci+vSKf1dtd+NUrBx17n HEVn5aIHFraR6Hkd34u+q5ahCpNViqsQ8mdZ+4jwhAE9j/2OAXeYl5JW3D/bFCkW rtU3RDTxQJ4J4SFY9CATso4SzUDaO2F7jurKbXsA8eAhWBs/cJrlAwPCFhqOBQ77 j6ZFm1dD7gSY2ohq7Zr+NDOg/JSMIKuy02IAmFoRkV9EzQR6ABQJRwgd34LjF3X3 LhUjJXExL3g5RIgs60mL =9hqE -----END PGP SIGNATURE----- --ADPimQnBB8pjfrw1tecVUfeeoBuxdW219-- --===============6413334223097334767== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============6413334223097334767==--