From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 828E1A0350; Fri, 5 Jun 2020 21:53:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 59BC01D50A; Fri, 5 Jun 2020 21:53:18 +0200 (CEST) Received: from mail-pl1-f181.google.com (mail-pl1-f181.google.com [209.85.214.181]) by dpdk.org (Postfix) with ESMTP id CA5C51D509 for <dev@dpdk.org>; Fri, 5 Jun 2020 21:53:16 +0200 (CEST) Received: by mail-pl1-f181.google.com with SMTP id n9so4141818plk.1 for <dev@dpdk.org>; Fri, 05 Jun 2020 12:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ZrvWIF3qgK+gam89LrcV8/PgUSRgA1Hl1pBFPaG34OQ=; b=xLPutvyr5jCn7MzAoiWawTHsJ2VFidTZnu5vJFfsCbr2KP8+/pzj8mdeMdeh3MOMN/ MaWSSmtwyg2Q3f7SylE9CjLnwgFAcKVYekcH2odsD2NMLHZX2xj9aVmjvM9qoVpAdN7I KXY7of/Vvc+kMTQwocD4bJlpj1wY9asRlJFLeE3EkZnKSEcBGzXx6Ws0CC51ttKsHYnO yoFB2pUhayEhLj5K0mMC0JkNL8V1Ap6iN5puTCIx1FBKtEjTgEBsMmkjYhnPA5BtS45e EY3M2TZvf+DdfX+ji9Da2RxIcd7gCn4+dJevjkK97SOkPili51OdghMAz3RvYwEovVMN k8hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ZrvWIF3qgK+gam89LrcV8/PgUSRgA1Hl1pBFPaG34OQ=; b=Go5egigZ3Sy3HLkoMJsXewIV9DubkABMfWi4O7omfPnqsL3c5dga3ssPyrs6JVgqEX Kttxrv/LWkNzo0JT/m1Wleki6ppTsRRckfLkIKhYXGSyOhJVwThal9xO5m8C/+2de+No WMk9/Ejg8K/enunD9PBhLCVaUsBYiC10KjycX7lDIXFY4tiNXq1wj2J+FEsxMo1Z46/a EfmLceIuXwuIuKpcuquPc5XNkRwJm801jKOtkZnbMgK4C4FEXH8ZqjT2hgJQ78NGzPCK RuUJ2aAZ3RO0eNjjLcmQAB2y2pMKqY/Unmzn9WEc9Fi6RXNFuPx6m51p5XBS1Adlfcid DoBQ== X-Gm-Message-State: AOAM532rG+13D0cKOm0VsblQogSJueQymP5LIp3lA7wSkpe2oHHebqei UBPhQ2IQh9swrS7OaKgNMjwGUw== X-Google-Smtp-Source: ABdhPJxnmzrZdeb93KVdfzpn+eqeg0XDJHeleVPwdPGYLd5uJbtBvOgOA9/+DFQwXbY788Yw4slVPA== X-Received: by 2002:a17:902:c14a:: with SMTP id 10mr11666314plj.222.1591386795177; Fri, 05 Jun 2020 12:53:15 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id o27sm331782pgd.18.2020.06.05.12.53.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Jun 2020 12:53:14 -0700 (PDT) Date: Fri, 5 Jun 2020 12:53:06 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: "Wiles, Keith" <keith.wiles@intel.com> Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, =?UTF-8?B?R2E=?= =?UTF-8?B?w6t0YW4=?= Rivet <grive@u256.net>, "dev@dpdk.org" <dev@dpdk.org> Message-ID: <20200605125306.7565e7a4@hermes.lan> In-Reply-To: <E768AD54-721A-48D1-AA1A-429229614EC9@intel.com> References: <20200604210200.25405-1-stephen@networkplumber.org> <20200604180409.4a2831c3@hermes.lan> <20200605104247.kilea5nfktlf7mlm@u256.net> <BYAPR11MB3301C3CEE4584EBB3067F2639A860@BYAPR11MB3301.namprd11.prod.outlook.com> <20200605093356.0e095587@hermes.lan> <BB2AB9C5-8FA1-4DD1-B477-4C94550A7510@intel.com> <20200605104510.150496d0@hermes.lan> <E768AD54-721A-48D1-AA1A-429229614EC9@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> On Fri, 5 Jun 2020 19:23:52 +0000 "Wiles, Keith" <keith.wiles@intel.com> wrote: > > On Jun 5, 2020, at 12:45 PM, Stephen Hemminger <stephen@networkplumber.org> wrote: > > > > On Fri, 5 Jun 2020 17:10:05 +0000 > > "Wiles, Keith" <keith.wiles@intel.com> wrote: > > > >>>>> > >>>>> I'd propose instead leader lcore - there is this idea that the leader > >>>>> is still a member of the team and will participate in the work. > >>>>> > >>>>> Leader / worker? > >>>>> > >>>> > >>>> I personally doubt such changes are needed at all. > >>>> Code churn will be massive for both DPDK itself and related user projects. > >>>> With no real gain in return, from my perspective. > >>>> Konstantin > >>>> > >>> > >>> 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. > >>> > >>> Increasing diversity and inclusion is an overarching goal of many organizations > >>> include my employer(Microsoft), the parent organization of DPDK(LF) > >>> and my values. > >>> > >>> Following values is more important than minor replacement of text in API. > >> > >> I feel like Konstantin is correct here. > >> > >> If we were using these terms for humans or groups of humans, then I would 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 and networking. > > > > Have to disagree, the words matter. This has been discussed many times. > > Please look at the footnotes from the Gnome post > > > > > > [0] - <https://www.cs.cmu.edu/~mjw/Language/NonSexist/vuw.non-sexist-language-guidelines.txt>, <https://twitter.com/justkelly_ok/status/933011085594066944> > > > > [1] - <https://github.com/django/django/pull/2692> > > [2] - <https://bugs.python.org/issue34605> > > > > [3] - <https://github.com/rust-lang-deprecated/rust-buildbot/issues/2>, <https://github.com/rust-community/foss-events-planner/issues/58> > > > > [4] - <https://twitter.com/ISCdotORG/status/942815837299253248> > > [5] - <https://gitlab.gnome.org/GNOME/geary/issues/324> > > You chopped off my last sentence in your reply. > > "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." > > So to be clear, I am not opposed to making this change, but wanted to point out the technical impacts of this change to DPDK as a whole. 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?