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 AB034A00C5; Fri, 5 Jun 2020 17:27:58 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EA3DC1D454; Fri, 5 Jun 2020 17:27:57 +0200 (CEST) Received: from mail-pf1-f194.google.com (mail-pf1-f194.google.com [209.85.210.194]) by dpdk.org (Postfix) with ESMTP id 3516E1BFF1 for ; Fri, 5 Jun 2020 17:27:56 +0200 (CEST) Received: by mail-pf1-f194.google.com with SMTP id h185so5060745pfg.2 for ; Fri, 05 Jun 2020 08:27:56 -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=5tWBxvV4bzN1ofK35dZpyeO1ZE+64DjvOKftVKvvbTU=; b=Uc7o++JCUO7rrBP6rEFzdwuZFcSx3JxPmM+Fi2LEAwgsZc1erEsaaLZRVDnP94U8Zx g2CwP1WN9W6QUXShpO/uilgR5BDU+upUnN1rTFM2gvxZlxowR0NSDQrRmBX27FdE9Whk Qp2kxbtt03VTcidiS27rPBk7xExjqSyGmzC3muNEbhGbtQKKW7AYlprfIcpcEXc4/kBY sL1vhCMpyDj9snzxQ9vfkFdg8sgA2I3ObEaXmEFBIY4LkxUMgt+g3awSGcnAsPsss2Pj BA6BGA6bF+w7mGeDWJSOYCZlEVwiWXeM4DbQi0gUsEpGeYBUtDCkScx32cx/0c63EDcz sTcA== 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=5tWBxvV4bzN1ofK35dZpyeO1ZE+64DjvOKftVKvvbTU=; b=AHyImO5+92Wos6DMPfbx+v6LWEZX4gbpiWa6tXWm1tZ3pgm0GynJWK8+pjQTqqAjU/ IL5ZctTzgBQ/cat5HoAxTyEp8YF5puCHcGOfUjwiPpbtDv4u06j0AJCu6pzcgMQ1KnrY hZSX9ULBKRznxcA1hGkPsr5JuPu4p1IxQ7mWJN+IV/BbFO+bN5fzYs1AaSwPUf90rKvC fMf7rEPakS/8p+SnNmbDMuRFV8LMVGrFjx5gFQYcGSCTpIA0mvjGz6Jpe9fnzrP5tfmI sEXjA5YscEs9FQb5LOc3xFqSrMx1bPEss2KVJwGYO32+bSB7iFbFJfiXee8e8BdAZM9Y 55rw== X-Gm-Message-State: AOAM530TSniJNQghaS4tgSuxiV6lwa/XeY4oXE9XAaExHV7xHMoYYt1H Q/+l6Igy1/4gQaSfjWZEf8FcQ6zgNQQ= X-Google-Smtp-Source: ABdhPJx5vEpkH9IWxSUKIrjPgpmnEV5nzTfspLoTgjYe4euHTMhf4xNbdB4IGCbG+k6URDitulELUA== X-Received: by 2002:a63:1a13:: with SMTP id a19mr9962805pga.350.1591370874639; Fri, 05 Jun 2020 08:27:54 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id b14sm11389pft.23.2020.06.05.08.27.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Jun 2020 08:27:54 -0700 (PDT) Date: Fri, 5 Jun 2020 08:27:45 -0700 From: Stephen Hemminger To: =?UTF-8?B?R2HDq3Rhbg==?= Rivet Cc: dev@dpdk.org Message-ID: <20200605082745.19466821@hermes.lan> In-Reply-To: <20200605104247.kilea5nfktlf7mlm@u256.net> References: <20200604210200.25405-1-stephen@networkplumber.org> <20200604180409.4a2831c3@hermes.lan> <20200605104247.kilea5nfktlf7mlm@u256.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 Fri, 5 Jun 2020 12:43:00 +0200 Ga=C3=ABtan Rivet wrote: > On 04/06/20 18:04 -0700, Stephen Hemminger wrote: > > I have a full patch that replaces the master/slave lcore > > naming (widely used in DPDK) with a better primary/secondary naming. > >=20 > > For now this is just a trial balloon to see what the impact would > > look like. The change mostly automated so likely that things > > are broken. > >=20 > > It is hard to break a change like this down, and still > > keep git bisection clean. > >=20 > > It keeps rte_master_lcore_id and RTE_FOREACH_SLAVE as deprecated > > items so that user code can still be built but they will be motivated > > to change. > >=20 > > Here is a sample of what it would look like: > > =20 >=20 > I think PRIMARY is a poor choice to describe the control thread. PRIMARY > is often used to designate the active element currently doing the work. > SECONDARY threads are also active threads doing equal dataplane work. >=20 > Another issue I see with primary / secondary is the ambiguity with > multi-process in DPDK. Doc readers could get confused about where a > primary / secondary thread is executed. >=20 > I think we could use instead DPDK-specific terminology. The lcore > organization is a little specific, with an lcore that does most init work > and spawns the others, but then runs the application like all others. >=20 > 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. >=20 > Leader / worker? >=20 Looking at Django the chose leader/follower. Other alternatives are: agency/operative hive/drone primary/handler conductor/doer captain/conscript schemer/patsies primary/replica