From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E03E3A0350; Fri, 5 Jun 2020 22:09:29 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E671E1D44D; Fri, 5 Jun 2020 22:09:28 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id E74F11D44A for ; Fri, 5 Jun 2020 22:09:26 +0200 (CEST) IronPort-SDR: HN08BQuDmrQwIUTAOjJMsPZ7pqBqMIeHI9mHCmatUbwVtTt2fiV0nenO+OjVCHTIA8FF3p+abi s309c2PhWZow== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jun 2020 13:09:25 -0700 IronPort-SDR: 1y2HC4+5rjgxQjSh3omhw1UJ9lEPj1qBJ6gddnUsjPCgc6zsv3jk9Jm3R6tVJpv/Kb4tmLZq0F xhGN11+jBHnQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,477,1583222400"; d="scan'208";a="273575353" Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga006.jf.intel.com with ESMTP; 05 Jun 2020 13:09:25 -0700 Received: from orsmsx113.amr.corp.intel.com (10.22.240.9) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 5 Jun 2020 13:09:24 -0700 Received: from ORSEDG002.ED.cps.intel.com (10.7.248.5) by ORSMSX113.amr.corp.intel.com (10.22.240.9) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 5 Jun 2020 13:09:24 -0700 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.173) by edgegateway.intel.com (134.134.137.101) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 5 Jun 2020 13:09:24 -0700 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QjxVx6N5iAnx3/CZ5MA6z837tDtXljJGc2qM+IcKyyCOP+L3BcKvcCEDgajuniao+rTpeSsbemGgbH7bdT7yA5f+HPO4htgCqJTRdAsDJl1wSXBPZIjRoNJROMpyvkwUVoBnOA6s4Aio7NNwmUxnH1eyu/5VpaTqXXgyi/YNVac9nhacTpCJwIjcazCuxbSXAAQ2hvy2FKrW4e0q2InYk1nh/UQuadu0axqRhD2+3rAq/hLYosaj46l3KlwZlveT8j9Mhe2QPxCL37NToJV+ofiRPI1ajZmAuA5mqWd7Znpz8Te1/OOP2GQuWMRlj0Mrp3QsG8HSlz7w4b7xftCHXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HWJp4Q5VoJkiXdkZOuFvB3qOISgfgv8cYKkJf0EWTS0=; b=LKXIHVr4A0p1Wn1FtXDEf9Poj05OZQvGZERbxrycPPjhXjSNlz5xJzANJ3eWCrL74ABU+//8zeuc3C33swul9DF2JNAzBB7FQGL2LiQ1LTQqOJ7WNqfm75kTZoZ6TlXiSNiHGQ8mk9uwRmDXwTTeiOQjCPMmVDd4G298PqBct0bfASU738x3tqA/F1M7RXcGqtj12r6pSha4Xth0/sNnv7LpyQthisQhFrXolVsH/7yqGidCQ04vBuEPlrL9FWSXWuspPZAR4wlGfqvwOMUza36/cbDZfnkffyLmsNHp4g2Dxu63nTZrVTAZzH8xx9Gs4NJWC+4D5kds69zzohJK6Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HWJp4Q5VoJkiXdkZOuFvB3qOISgfgv8cYKkJf0EWTS0=; b=NFS79sE383OQjmkVMDI60pg7vuX7cTgzwXDMtLhnrMsrorpbl5BMCWjN8kghcG4KJ5o2lAT18Nqub1XMP0ZqLMDHucybV4tR9vzX321MtQS0F+nQ3mwdabEMEkeOqbkjvJ672fS3Q2k9wom5tOs7UXQS/Fw/UH+ahWlS5prIWJ8= Received: from DM6PR11MB4593.namprd11.prod.outlook.com (2603:10b6:5:2a3::8) by DM6PR11MB4625.namprd11.prod.outlook.com (2603:10b6:5:2a8::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.18; Fri, 5 Jun 2020 20:09:23 +0000 Received: from DM6PR11MB4593.namprd11.prod.outlook.com ([fe80::acee:4fa2:2a9e:7cd6]) by DM6PR11MB4593.namprd11.prod.outlook.com ([fe80::acee:4fa2:2a9e:7cd6%3]) with mapi id 15.20.3066.018; Fri, 5 Jun 2020 20:09:23 +0000 From: "Wiles, Keith" To: Stephen Hemminger CC: "Ananyev, Konstantin" , =?iso-8859-1?Q?Ga=EBtan_Rivet?= , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC] replace master/slave with primary/secondary Thread-Index: AQHWOtVSEChsxd1g5kqTS/uzZaLX36jJ1n8AgAAI5QCAAFknAIAAChqAgAAJzQCAABuTgIAACCwAgAAEiwA= Date: Fri, 5 Jun 2020 20:09:23 +0000 Message-ID: <0B28BE54-EB71-49AE-9FEC-FBA4F7ABC41F@intel.com> References: <20200604210200.25405-1-stephen@networkplumber.org> <20200604180409.4a2831c3@hermes.lan> <20200605104247.kilea5nfktlf7mlm@u256.net> <20200605093356.0e095587@hermes.lan> <20200605104510.150496d0@hermes.lan> <20200605125306.7565e7a4@hermes.lan> In-Reply-To: <20200605125306.7565e7a4@hermes.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: networkplumber.org; dkim=none (message not signed) header.d=none;networkplumber.org; dmarc=none action=none header.from=intel.com; x-originating-ip: [47.24.6.94] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 71c39a16-64d5-4f73-6dee-08d8098c571d x-ms-traffictypediagnostic: DM6PR11MB4625: x-ld-processed: 46c98d88-e344-4ed4-8496-4ed7712e255d,ExtAddr x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:2657; x-forefront-prvs: 0425A67DEF x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: JN2nTzDJqA+o1OiXvH5A7Z5GKer6jb4ohklCMDk9RC+Vioz2RrvfavUkqgMPW9e7F1A+nN6l+/kc3P3XIIXMpqBZBWae2MqpG1ZI+++9jPDCqVBpEmAXAvrvEedkfR7FeGBhqKjo74b+K2lR3MqQD1QbIaLFvHoGXpruNg+GwG/yRFUW+TQ88XMIcEgTO7yfqdBf9K+t0k9IBrunkR+VX13kQoxJBfmlcBkWXD+PbrG4WoY6DUKw9mVPM9L7B4CWXbGZ5VJ87H7o8r4Fs4grxRTCEI5xf5RzqmRHN7QX17zo7WGM2b754eOJCfq4EWBMRQwVTtNT3GS3lqS881bSGXmO6vyXPToOQlRC0taG1eyfYsQlE62D8Xar73RR1EujfNKBnxcWdPyfdo2fDunVzQ== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR11MB4593.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(396003)(39860400002)(366004)(136003)(376002)(346002)(66556008)(66476007)(8936002)(2616005)(71200400001)(26005)(6512007)(186003)(66446008)(8676002)(86362001)(76116006)(45080400002)(91956017)(36756003)(33656002)(478600001)(6506007)(53546011)(4326008)(6916009)(83380400001)(54906003)(5660300002)(2906002)(6486002)(66946007)(316002)(64756008); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: pRIW5csZ97Qdj7WOecKkOsxuwlhOnUfqkuiE+ZSOAj16RnaMfPBZtN3mLA314y9uNq87DGBfxMEKZOHaaEXCj+sA2wzS7AfKx1SSryQEdpm4B6F98G3C9VzKO1NPgsQrmfmwCH5NnutpWIrgDQbqBFo5jffvC34llpcicT8kmcMCFGrUJFHPmkmrxBR/Ck1TO0UMIgmdrUhdIynrcWmeFnjeWkLBIrpdp6JSWrYfHmjR15X9MyJ+kCrPiWnwot9WKu9pIlGol52fNlgbLyk8j0S2YKkdmeelQ5xSgbtZNaL5xm7NdWU+KSMefEsw3cl2Qj0vtz6AxM3oh+bkQ9ZVhmGyDC8KGiVe4zcYDdWj4XlZVv/6rnqtS5qp8OCspC/lZMPbyB8nTYshyNfhdtcsDg45mmWcSf+9NC5f6tAo34IIcTaYQS3xa0XIY1nxKGyc1O9rzeh57V3q8qQSG62lW4gNErawFPH0mkW6LFHs1LQ= Content-Type: text/plain; charset="iso-8859-1" Content-ID: <214E3CE8A5F68149A17F9DB9DC4C1F71@namprd11.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 71c39a16-64d5-4f73-6dee-08d8098c571d X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2020 20:09:23.2750 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: fuStWvhL3qk0MljDAneqXWSlUg86XH15B6Cdnyq/aSrmWaMggsaVUS6SERn52BUDqA90+Z4Ionq8VdRoe4Qo2w== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4625 X-OriginatorOrg: intel.com Subject: Re: [dpdk-dev] [RFC] replace master/slave with primary/secondary X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > On Jun 5, 2020, at 2:53 PM, Stephen Hemminger wrote: >=20 > On Fri, 5 Jun 2020 19:23:52 +0000 > "Wiles, Keith" wrote: >=20 >>> On Jun 5, 2020, at 12:45 PM, Stephen Hemminger wrote: >>>=20 >>> On Fri, 5 Jun 2020 17:10:05 +0000 >>> "Wiles, Keith" wrote: >>>=20 >>>>>>>=20 >>>>>>> I'd propose instead leader lcore - there is this idea that the lead= er >>>>>>> is still a member of the team and will participate in the work. >>>>>>>=20 >>>>>>> Leader / worker? >>>>>>>=20 >>>>>>=20 >>>>>> I personally doubt such changes are needed at all. >>>>>> Code churn will be massive for both DPDK itself and related user pro= jects. >>>>>> With no real gain in return, from my perspective. >>>>>> Konstantin >>>>>>=20 >>>>>=20 >>>>> Your concern is valid but the issue does need to be addressed. >>>>> If now when? This is as a good a time as any to do it. >>>>>=20 >>>>> Increasing diversity and inclusion is an overarching goal of many org= anizations >>>>> include my employer(Microsoft), the parent organization of DPDK(LF) >>>>> and my values. >>>>>=20 >>>>> Following values is more important than minor replacement of text in = API. =20 >>>>=20 >>>> I feel like Konstantin is correct here. >>>>=20 >>>> If we were using these terms for humans or groups of humans, then I wo= uld agree they should be changed. We need to take into account the context = of the reference to these words. I agree some words should never be used in= any context, but these terms are very reasonable in the context of DPDK an= d networking. =20 >>>=20 >>> Have to disagree, the words matter. This has been discussed many times. >>> Please look at the footnotes from the Gnome post >>>=20 >>>=20 >>> [0] - , >>>=20 >>> [1] - >>> [2] - >>>=20 >>> [3] - ,= >>>=20 >>> [4] - >>> [5] - =20 >>=20 >> You chopped off my last sentence in your reply. >>=20 >> "If everyone wants to accept the code churn (and it will effect a large = number of applications, plus back porting will be more difficult IMO), then= we can do it." >>=20 >> So to be clear, I am not opposed to making this change, but wanted to po= int out the technical impacts of this change to DPDK as a whole. >=20 >=20 > Thanks, my editing was not intended to be a way to stifling your response= . > How many applications try to support multiple DPDK major versions at once= ? >=20 NP, I understand it was not intended, but wanted to make sure it was not lo= st. In Pktgen I try to support back to 18.11 release and some have asked for 18= .04, one asked for 16.04 :-) I most likely do not do it very well, but I tr= y given the limited time I have. The big churn happened in 19.05 I think when all of the APIs and defines ch= anged. It took me a few days to create a compat file to support backward co= mpatibility . I try to tell everyone I only support the latest release of DPDK and latest= release of Pktgen, but that does not fly very well for some customers. I would hope we can make this change and create methods to allow for suppor= ting backward compatibility without every application having to create the = compatibility support themselves. Let me know how I can help, Thanks