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 E9F51456AC; Thu, 25 Jul 2024 18:21:09 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B3696435F7; Thu, 25 Jul 2024 18:21:02 +0200 (CEST) Received: from smtp-fw-9106.amazon.com (smtp-fw-9106.amazon.com [207.171.188.206]) by mails.dpdk.org (Postfix) with ESMTP id 533E1402AB for ; Thu, 25 Jul 2024 18:02:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1721923368; x=1753459368; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=6ZaO0ApGbr0/045LQwWNQdrR0Pa82Yi+yVWq7egMEH4=; b=YCNNpdBMQa1K4fGgcNROtsO7IdQIQuJZ7G3oKFv58ip1sRTpqcrMAp5d gdbYV0QImTVO2VyNbg1+sry2PTrubsnN77UGaBvLFYbzbYLeWFyyjOk3n vcusfoWZ5wvaoSrnZ1nHjHN++VBUdtXF9qccANGVcDYJ+ScnG5N5Snjw5 I=; X-IronPort-AV: E=Sophos;i="6.09,236,1716249600"; d="scan'208";a="744679844" Received: from pdx4-co-svc-p1-lb2-vlan2.amazon.com (HELO smtpout.prod.us-east-1.prod.farcaster.email.amazon.dev) ([10.25.36.210]) by smtp-border-fw-9106.sea19.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jul 2024 16:02:41 +0000 Received: from EX19MTAEUA002.ant.amazon.com [10.0.43.254:36603] by smtpin.naws.eu-west-1.prod.farcaster.email.amazon.dev [10.0.44.212:2525] with esmtp (Farcaster) id a514c7bf-1c61-41c8-b6e3-294d72bf5f65; Thu, 25 Jul 2024 16:02:39 +0000 (UTC) X-Farcaster-Flow-ID: a514c7bf-1c61-41c8-b6e3-294d72bf5f65 Received: from EX19D007EUA003.ant.amazon.com (10.252.50.8) by EX19MTAEUA002.ant.amazon.com (10.252.50.126) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.34; Thu, 25 Jul 2024 16:02:39 +0000 Received: from EX19D007EUA004.ant.amazon.com (10.252.50.76) by EX19D007EUA003.ant.amazon.com (10.252.50.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.34; Thu, 25 Jul 2024 16:02:38 +0000 Received: from EX19D007EUA004.ant.amazon.com ([fe80::d9f5:ab17:b5c0:4f4d]) by EX19D007EUA004.ant.amazon.com ([fe80::d9f5:ab17:b5c0:4f4d%3]) with mapi id 15.02.1258.034; Thu, 25 Jul 2024 16:02:38 +0000 From: "Brandes, Shai" To: "dev@dpdk.org" Subject: Question regarding the status of Hotplug on multi-processes Thread-Topic: Question regarding the status of Hotplug on multi-processes Thread-Index: AdreqSYxjw7Z5rDVTr2tWxELpICvGQ== Date: Thu, 25 Jul 2024 16:02:38 +0000 Message-ID: <590f548d83ac42cc819e549d3c0392f9@amazon.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.85.143.175] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 Hi all, I hope this email finds you well. We would like to understand the status of Hotplug on multi-processes: - 18.11 RN https://doc.dpdk.org/guides-23.11/rel_notes/release_18_11.html s= tates that it added support for device multi-process hotplug. - DTS test plan https://doc.dpdk.org/dts/test_plans/hotplug_mp_test_plan.ht= ml states that Hotplug on multi-processes is not expected to function. - When testing both our ENA device and Intel device, the multiprocess does = not seem to function after hotplug (both fail with the same error in the se= condary process that it is unable to reach the primary process). Our understanding is that there is a gap with MP. If this is correct, is th= ere any plan to close this gap? Thanks for your time and consideration, Shai