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 3A543A0542; Sat, 8 Oct 2022 16:48:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DD3164021F; Sat, 8 Oct 2022 16:48:34 +0200 (CEST) Received: from out203-205-221-192.mail.qq.com (out203-205-221-192.mail.qq.com [203.205.221.192]) by mails.dpdk.org (Postfix) with ESMTP id 64CB94021E for ; Sat, 8 Oct 2022 16:48:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s201512; t=1665240509; bh=jdVtnLdW2gFSOQCUjzAs4bzZPA2DhYiRc9yG3AkaO1Q=; h=Date:From:To:Subject; b=qCyxjfJt0nlbIlOck1+OFV/2rH0cJiNwI1eeOI8ep68aGZav6Oc0CC9bW27hEN1Q0 45s/IBTgZnwzXIy+N4tWB8J8zok8StJ01iwwcNx14DyDK9uR4eKPFJX9y/fiNYYtL1 mpsxaNyneRsIgEWo39jPxOpk+6R9UcyJ/g8y39tk= Received: from vscode. ([171.223.95.86]) by newxmesmtplogicsvrsza31.qq.com (NewEsmtp) with SMTP id C168082F; Sat, 08 Oct 2022 22:48:22 +0800 X-QQ-mid: xmsmtpt1665240502tby8gsk3j Message-ID: X-QQ-XMAILINFO: MmpliBmRb3iClzmpAW0urkZIr5q0u8noZ+tcnM8ugn+BBBT1L+hDmmgOa5lFsE Zjk+srXZASTsm11GNT+b7RShArpnteKX4PsncP6mQRrLYeUa820wUHbQER+JiI6UsUJUPK3KcTA8 lM7CIpkP5s+N05XTOe3RzZo8ugpXmf9OkTaWZ/iKqikEoT36VIrjjp8xdF6XCURaw+5uNY8ddeD9 zJQut81U/TDjfyWXnXHUzCAi0O8vHvIEIlLFjaTB83faayX0g3UmIWySdXNOuOQR1YZCpOkTiVTP bZw4NXOK5u96aUKoU4+aggPe4Zy95Cbf3sntjeYbORX1zV0UkjxMXn7dPRnI2MspLnR9E+poOCji ePwr4bkigFn1qnS1Wb3GoK7wx3mHNcc8JK53qMr7kxprtxAeDIp4BquDzFM8hzJLB+PezBFaAThW XgzKXV+3onosWjZWPTi7WzgubVRkoJBsNbIRw6on14EppLySmPbxMo/ccl9NGkFYEtgx4XIxcJ7k Z6PBvksxKpe9ifxMPXW0a2NdRP8QPZC4x/hvpiVL6WQd5vgG+CO15JVn+5L+xhJZnUDLcDMAN2xN TZ6aHyd2F7QxgiNXmOYg0u0CfkdrEDh4q3OyzzZDILn05XLGM32KJULXpDdcI71wwJLTvgYm56nk HlgRiiGyI75wk/AUPMWGv1x2+khu5SfEJGhdtDlc+Bl1yAx40Siqd9aBYy2aGVe3JHLGMzFZGOq8 VYkV+qnHdbfY/NiSAcROicrYAfGEuYTho8BPA89cr5hAtrhLVAnYwQJfqvy8L8FStlJqW0R01/of mM0IjkcPFh1CerIAiIKY+JA80R2zeg388yCDqqJeEahibxtJWdQ9xolZzdKnuFJOxGClwxeGzpxV dYWZyHqf3qd3mgLJxkkWf2AOudIT/DVHHkuTdIBVrhVzFp2KO0nuR7XILf128PbMkun8V6xHkRzI O1NvEdovnwFyx+dYclHjA6aT+HRG+qXT4W2qcn0Qk5zXkKqtOcgA== Date: Sat, 8 Oct 2022 14:48:22 +0000 From: Cheng Li To: dev@dpdk.org Subject: Any way to promote secondary process to primary process X-OQ-MSGID: <20221008144822.GA22333@vscode.> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello, I would like to kill the primary process and then promote the seconary process to primary. After checking the apis in dpdk source code, I think dpdk doesn't provide the promote interface. Any one knows why we don't have this interface? No usage scenario? or it's impossible to implement? Bellow is my scenario: I would like to upgrade my application(openvswitch). Because the hugepage initialization and dev probe is expensive, the application down time is very long(could be more than 10 seconds). So I would like to launch the new application(upgrade version) as secondary process, while keep the old application still running. New application shares memory from old application, so it can use the hugepage and already probed devices. Imediately old process is killed, new application starts forward packets. After old process(primary process) is killed, we would like to promote the new process from secondary to primary. Thanks, Cheng