From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C77F5A0548 for ; Thu, 4 Nov 2021 09:30:21 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B7541410D5; Thu, 4 Nov 2021 09:30:21 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 42D7240DFD for ; Thu, 4 Nov 2021 09:30:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1636014619; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=F4kNpx53NLHCNzwb/O2A/9YXObPQ1Gnch+N+11Io8l8=; b=dGlJ8beuiPkb5yUzRrTcvzSu6mIMVJTrxmeQi9WkgCQYgSfBq7sy4q/7/s0ktl/3yaIkhN oycvFIa/fAMca4Hz1UyR0laAlzsKVLLstve2UYT6+Z9nqnGfGv1yjXbRFlO/jR+/njB5FB nIjUKmZ30KHVN6SmpDTu3kfIK0FOXBM= Received: from mail-lj1-f199.google.com (mail-lj1-f199.google.com [209.85.208.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-388-O2zGYJ46MMmfbMwv-v-b-Q-1; Thu, 04 Nov 2021 04:30:18 -0400 X-MC-Unique: O2zGYJ46MMmfbMwv-v-b-Q-1 Received: by mail-lj1-f199.google.com with SMTP id v2-20020a2e5042000000b00216bb21d8b8so1975720ljd.13 for ; Thu, 04 Nov 2021 01:30:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=F4kNpx53NLHCNzwb/O2A/9YXObPQ1Gnch+N+11Io8l8=; b=naX2r2ZjYT/hCAqsvkhd0hfgOmyTBYEETTKDh88z9cq7/24gmr+z1GY4ZvbxVPSKjE eTF+5GVCpi+a6a0b4oHPITRGRcQ+bj7pX5iczqzBrgMM5354ApTu5kSpnyQ4xEiVjc7z qAGWthHhbkd+JN3xST4r0TH1bfxSiZq6biwpm1nMIawsuIcVs03wNAgQb1mKlPYWPO+R fYtwSrz5vnD+yQDaEoQ8ImUZ+aYCTrOPYBrhtnUueuskYJgNfq8H8KT3jibf02MhMSUC njIer+eyI849zw9dBo5D1t3MRRzFaa9jUKW+4tTun8Rn+ug0GUAxCjGbKCdts+SBqlJu hQMA== X-Gm-Message-State: AOAM53388UntHIFo95BBiA2rno60rSS+YzKyEvw7MApedYOsoPDUQd3s RhpA0xoLjuackjOdCWI1K1pFN0igX2eXeZNuuEUeBMaB+gxCigUUtD3DE3xwwMnqYeX8W2YE8G7 ZePtuvvnTQuH6sXXb3KmdGA== X-Received: by 2002:a2e:7f1b:: with SMTP id a27mr50952296ljd.55.1636014617107; Thu, 04 Nov 2021 01:30:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz+aFA8K3WUpUfw8h7tDiEh8Mixcyd2L1LOjNldLnD+uBccwV734xi8BgrMlm8wORQQT4zoO5ue5q2C5So0UGo= X-Received: by 2002:a2e:7f1b:: with SMTP id a27mr50952276ljd.55.1636014616928; Thu, 04 Nov 2021 01:30:16 -0700 (PDT) MIME-Version: 1.0 References: <413ad5cc.905b.17cea09869a.Coremail.15310488637@163.com> In-Reply-To: <413ad5cc.905b.17cea09869a.Coremail.15310488637@163.com> From: David Marchand Date: Thu, 4 Nov 2021 09:30:05 +0100 Message-ID: Subject: Re: Aboud DPDK Multi-Process To: =?UTF-8?B?6LWW6aaZ5q2m?= <15310488637@163.com> Cc: users , "Burakov, Anatoly" , Bruce Richardson Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Archived-At: List-Archive: On Thu, Nov 4, 2021 at 9:21 AM =E8=B5=96=E9=A6=99=E6=AD=A6 <15310488637@163= .com> wrote: > > Hello, I have a question about dpdk multi-process. After starting the pri= mary process and the secondary process, when the current primary process ex= its, how does the secondary process become a new primary process to make th= e program continue? Hope to get your answer, thank you=EF=BC=81 Not sure why you need this, but DPDK won't do for you. The process type is decided once at DPDK init, and that is something that affects how your program behaves after. Switching type while running would break assumptions in the DPDK drivers and libraries. One thing that comes to mind, is that you could try to call rte_eal_cleanup() and call rte_eal_init() again. This is probably something that is not tested (so I'd expect issues, maybe leaks etc..). But then, you probably want to restart your process entirely. --=20 David Marchand