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 3403B45BA3 for ; Tue, 22 Oct 2024 17:20:16 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CA4BE4029B; Tue, 22 Oct 2024 17:20:15 +0200 (CEST) Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by mails.dpdk.org (Postfix) with ESMTP id B39D04029A for ; Tue, 22 Oct 2024 17:20:13 +0200 (CEST) Received: by mail-pl1-f176.google.com with SMTP id d9443c01a7336-20c693b68f5so61847445ad.1 for ; Tue, 22 Oct 2024 08:20:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1729610412; x=1730215212; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=Rvg63AVVAXO2a7kpS3xhJlfuxme1uQ+0MAHEvX806to=; b=G8a5cLzX3Z6bESulhkaOILXzVO1rcFCoULY9U1wQXGlq7ebK4OmJubeOgh+1YXGNyV x1oK6aVkS4poHJ/gjRE8gS10WQt3Uf5myEHeHT1XmfMvJ+zx99Q3gP6aqJAM0DbwjVWg W5TYZQ+28kZaTtlgeieV/sl6ErGUIbLvStH6f983mp3Fu5NIHH7INmCYyYVyAtdaiuTG gQ/stmKiH7zLhYYHjzu0WWUcbOyYXkmivOVO0XGjjqHOHXLVFEcwZoSC6YgmyExV7wFP oqCNudaYJUlnodNXTk+RukejpgZ/gJ9l1b6wuogtJbXX6BnI7UijeGMyHefWbdEgWz2R 94+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729610412; x=1730215212; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Rvg63AVVAXO2a7kpS3xhJlfuxme1uQ+0MAHEvX806to=; b=kSBSyB4JtwgOetdpTT0o07g5ZR8yL0SW8wjKGt6b6JFmyTrOTGFcKGZhZ8xFK14HOO IVZnORP9ijXKbPVS/tVLXQbvJ5azydELure9s/pH084iVkX99oo5NLMMUe0XHT52ei7A zfSPFZHOSOXeStQoZGvj25n/NfqcEd56NCJYvL6teiELkeaRWymiSPsu1ZRZYh3LPcs5 L/f0sWkoVGALeaYa4t5gGTeto3B5pN6uLSJYMSZmaNXwo9G32nPOr7vWqkyUne52IMUg 5ZbmfJq3HlP0sThhmtKC6yUzpJSWa1U/jeJWQnrQJRnwWdUi4YcNKFEVYCr6RwJsaIXd zEYw== X-Gm-Message-State: AOJu0Yx9Bp+MzRTAgszqtiXqwsO3y/hR/tRGnkfnIP1cUAzmYQV7vEWE Btn/lF+VJmTkvfCaMVu4Qi+Kli5+4dvEskd/7D1GHs8HyUgBUfyaJ1cjUFlf9Ac= X-Google-Smtp-Source: AGHT+IFTNN/7t4OHfrsOXmLqJ3/PpNpBRd44L0UfFGJjiDSfzf9sE2Npaxd/iJtpmH4g1Z8SGiv3Hg== X-Received: by 2002:a17:902:c407:b0:207:4c7c:743b with SMTP id d9443c01a7336-20e982915c8mr32071605ad.0.1729610412451; Tue, 22 Oct 2024 08:20:12 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-20e7f0c0e09sm44090605ad.139.2024.10.22.08.20.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2024 08:20:12 -0700 (PDT) Date: Tue, 22 Oct 2024 08:20:10 -0700 From: Stephen Hemminger To: jinag Cc: users@dpdk.org Subject: Re: Does DPDK support forking processes after executing rte_eal_init() ? Message-ID: <20241022082010.5f8bd608@hermes.local> In-Reply-To: <15e742c4.35cc.192987700b5.Coremail.jinag12138@163.com> References: <15e742c4.35cc.192987700b5.Coremail.jinag12138@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Thu, 17 Oct 2024 11:13:08 +0800 (CST) jinag wrote: > Hi ALL: > 1. child process execute rte_eal_init() as dpdk secondary processes. > 2. child process do not execute any dpdk-related function. No, don't fork after starting rte_eal_init() you will break lots of things.